Implement the ClientTypeBypass Integration Test with ChromeDriver |
|||||
Issue descriptionGet the client type with the first request, then check bypass on the appropriate test page New File Name: bypass.py New Method Name: testClientTypeBypass Telemetry PageSet: https://cs.chromium.org/chromium/src/tools/chrome_proxy/integration_tests/chrome_proxy_pagesets/client_type.py Telemetry Benchmark: https://cs.chromium.org/chromium/src/tools/chrome_proxy/integration_tests/chrome_proxy_benchmark.py?l=42 Telemetry Measurement: https://cs.chromium.org/chromium/src/tools/chrome_proxy/integration_tests/chrome_proxy_measurements.py?q=file:tools/chrome_proxy/integration_tests/chrome_proxy_measurements.py+"class+ChromeProxyClientType" Telemetry Metric: https://cs.chromium.org/chromium/src/tools/chrome_proxy/integration_tests/chrome_proxy_metrics.py?q=file:tools/chrome_proxy/integration_tests/chrome_proxy_metrics.py+AddResultsForClientType (This bug was automatically generated.)
,
Feb 23 2017
,
Apr 6 2017
Moving to jiewu@ who's interested in working on this.
,
Apr 30 2017
,
May 10 2017
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by robertogden@chromium.org
, Jan 12 2017Labels: Integration-Test Pri-2 Type-Feature
Status: Available (was: Untriaged)