Check that Chrome uses QUIC correctly when connecting to a proxy that supports QUIC. New File Name: quic.py New Method Name: testQuicTransaction Telemetry PageSet: https://cs.chromium.org/chromium/src/tools/chrome_proxy/integration_tests/chrome_proxy_pagesets/quic.py Telemetry Benchmark: https://cs.chromium.org/chromium/src/tools/chrome_proxy/integration_tests/chrome_proxy_benchmark.py?l=358 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+ChromeProxyQuicTransaction" 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+AddResultsForQuicTransaction (This bug was automatically generated.)
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/e9ee3d63b09c9ef3f9dafc84bf7cfa83c89203fc commit e9ee3d63b09c9ef3f9dafc84bf7cfa83c89203fc Author: tbansal <tbansal@chromium.org> Date: Fri Mar 17 22:21:37 2017 Client config and QUIC transaction integration tests BUG= 680570 , 680564 Review-Url: https://codereview.chromium.org/2754803004 Cr-Commit-Position: refs/heads/master@{#457892} [modify] https://crrev.com/e9ee3d63b09c9ef3f9dafc84bf7cfa83c89203fc/tools/chrome_proxy/webdriver/smoke.py
Comment 1 by robertogden@chromium.org
, Jan 12 2017Labels: Integration-Test Pri-2 Type-Feature
Status: Available (was: Untriaged)