| Index: Tools/Scripts/webkitpy/thirdparty/webpagereplay/perftracker/README
|
| diff --git a/Tools/Scripts/webkitpy/thirdparty/webpagereplay/perftracker/README b/Tools/Scripts/webkitpy/thirdparty/webpagereplay/perftracker/README
|
| new file mode 100644
|
| index 0000000000000000000000000000000000000000..d6efd1b8b6afe36606342da6ef9c8ae4a1a83d1d
|
| --- /dev/null
|
| +++ b/Tools/Scripts/webkitpy/thirdparty/webpagereplay/perftracker/README
|
| @@ -0,0 +1,21 @@
|
| +The PerfTracker application is an automated test run framework to measure
|
| +network performance through Chromium using WebPageReplay and storing results
|
| +in a Google AppEngine service.
|
| +
|
| +CONTENTS:
|
| +app/ - This is the AppEngine application for collecting results.
|
| +extension/ - This is an extension to run inside of Chrome which will drive
|
| + the test automation.
|
| +runner.py - The main glue to run the entire harness
|
| +runner_cfg.py - Configuration to the harness. Edit this file!
|
| +
|
| +
|
| +HOW TO USE:
|
| +First, you'll need to create your own Google AppEngine service. You can use
|
| +the dev_appserver.py before using a real service.
|
| +
|
| +Second, you'll need to modify runner_cfg.py to capture the configurations you
|
| +wish to test, and to point at the appropriate servers and such.
|
| +
|
| +Third, run runner.py!
|
| +
|
|
|