Add HTML5 integration test

tools/chrome_proxy/webdriver/html5.py

Index: tools/chrome_proxy/webdriver/html5.py
diff --git a/tools/chrome_proxy/webdriver/html5.py b/tools/chrome_proxy/webdriver/html5.py
new file mode 100644
index 0000000000000000000000000000000000000000..b802fdf63f6b5232487d070b5a0eb60521bfda60
--- /dev/null
+++ b/tools/chrome_proxy/webdriver/html5.py
@@ -0,0 +1,28 @@
+# Copyright 2017 The Chromium Authors. All rights reserved.
+# Use of this source code is governed by a BSD-style license that can be
+# found in the LICENSE file.
+
+import common
+from common import TestDriver
+from common import IntegrationTest
+
+
+class HTML5(IntegrationTest):
+
+  # This test site has a div with id="pointsPanel" that is rendered if the
+  # browser is capable of using HTML5.
+  def testHTML5(self):
+    with TestDriver() as t:
+      t.AddChromeArg('--enable-spdy-proxy-auth')
+      t.LoadURL('http://html5test.com/')
+      t.WaitForJavascriptExpression(
+        'document.getElementsByClassName("pointsPanel")', 15)
+      for response in t.GetHTTPResponses():
+        # Site has a lot on it, filter out everything else and ignore the XHR
+        # form post.
+        if (response.url.startswith('http://html5test.com/') and

[RyanSturm, 2017/01/25 21:06:50]

If there is a way to filter to the exact match instead of startswith, we might
be better off.

In general, POSTs won't be handled which could be forms and not XHR maybe (I
don't know), but at the same time, all this has to test is that the main
resource is tested, hence the exact match.

I think it will be more robust if we only test one resource if we are using a
webpage that can change unexpectedly.

[Robert Ogden, 2017/01/25 23:05:30]

Done.

+            not response.WasXHR()):
+          self.assertHasChromeProxyViaHeader(response)
+
+if __name__ == '__main__':
+  IntegrationTest.RunAllTests()