diff options
author | fdeng@chromium.org <fdeng@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-09-07 20:42:27 +0000 |
---|---|---|
committer | fdeng@chromium.org <fdeng@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-09-07 20:42:27 +0000 |
commit | 25da1685160963a14710a128977525ea55aee091 (patch) | |
tree | dc4192b72fdaa8f5e9b69c085b815fa88da18732 /win8/metro_driver/settings_handler.h | |
parent | 65d3bfbb0137b6ebab73fe2c8e4c841250a84498 (diff) | |
download | chromium_src-25da1685160963a14710a128977525ea55aee091.zip chromium_src-25da1685160963a14710a128977525ea55aee091.tar.gz chromium_src-25da1685160963a14710a128977525ea55aee091.tar.bz2 |
Run Chrome Endure tests with network simulation via Web Page Replay.
Previously Chrome Endure tests always connect to a live website which may change over time.
This CL is to simulate the network via Web Page Replay. The idea is to use WPR to record webapp interactions of a test and replay them in the future runs of the test.
Environment variables:
WPR_RECORD: set this environment variable if you wan to record webapp interactions of tests via Web Page Replay.
ENDURE_NO_WPR: set this value if you DO NOT want to run the endure tests against the Web Page Replay server.
Examples:
1. ENDURE_NO_WPR=any_value python perf_endure.py perf_endure.ChromeEndureGmailTest
Tests will connect to live site.
2. WPR_RECORD=any_value python perf_endure.py perf_endure.ChromeEndureGmailTest
Web Page Replay will start in record mode and a Web Page Replay archive will be created.
3. python perf_endure.py perf_endure.ChromeEndureGmailTest
By default, tests will run against Web Page Replay server.
BUG=None
TEST=ran all tests in perf_endure.py in three modes: record, replay, no web page replay
NOTRY=true
Review URL: https://chromiumcodereview.appspot.com/10803002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@155473 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'win8/metro_driver/settings_handler.h')
0 files changed, 0 insertions, 0 deletions