Implement the PassThrough Integration Test with ChromeDriver |
||||||
Issue descriptionCorrectness measurement for Chrome-Proxy-Accept-Transform identity directives. This test verifies that "identity" in the Chrome-Proxy-Accept-Transform request header causes a resource to be loaded without Data Reduction Proxy transformations New File Name: smoke.py New Method Name: testPassThrough Telemetry PageSet: https://cs.chromium.org/chromium/src/tools/chrome_proxy/integration_tests/chrome_proxy_pagesets/pass_through.py Telemetry Benchmark: https://cs.chromium.org/chromium/src/tools/chrome_proxy/integration_tests/chrome_proxy_benchmark.py?l=106 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+ChromeProxyPassThrough" 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+AddResultsForPassThrough (This bug was automatically generated.)
,
Jan 23 2017
,
Feb 23 2017
,
Apr 6 2017
Moving to jiewu@ who's interested in working on this.
,
Apr 30 2017
,
May 1 2017
We need a server side integration test instead of a client one for verifying "identity" in the Chrome-Proxy-Accept-Transform request header causes a resource to be loaded without Data Reduction Proxy transformations. As a note though, we don't ever set Chrome-Proxy-Accept-Transform:identitiy in the client (instead CPAT is left off). If it's not testing any client functionality, I think this would be better suited to be a server-side integration test. Thus, I created the following bug: https://b.corp.google.com/issues/37858015 |
||||||
►
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)