Confirmed users
1,927
edits
Auto-tools/Projects/SpeedTests: Difference between revisions
Auto-tools/Projects/SpeedTests (view source)
Revision as of 22:02, 29 September 2011
, 29 September 2011→Usage
(→Usage) |
(→Usage) |
||
| Line 49: | Line 49: | ||
The client can be started by just running "python speedtests.py". If you don't want to run all the browsers, you can append a list of desired browsers, e.g. "python speedtests.py nightly 'internet explorer' chrome". You can also use the "-t" option to provide a test path. Note that in this case speedtests.py does not fetch the test list from the server, so you have to provide the full (relative) path, e.g. -t test262/default.html. | The client can be started by just running "python speedtests.py". If you don't want to run all the browsers, you can append a list of desired browsers, e.g. "python speedtests.py nightly 'internet explorer' chrome". You can also use the "-t" option to provide a test path. Note that in this case speedtests.py does not fetch the test list from the server, so you have to provide the full (relative) path, e.g. -t test262/default.html. | ||
Adding "--noresults" will prevent the client from sending the results back to the test server. Results will still be output to the terminal. | |||
It can also be run in test mode by appending the "--testmode" option. This causes the server to return simple test pages that do not run any tests but exercise the framework itself, namely, ensuring that the browser can deal with popups, accessing localhost, etc. | It can also be run in test mode by appending the "--testmode" option. This causes the server to return simple test pages that do not run any tests but exercise the framework itself, namely, ensuring that the browser can deal with popups, accessing localhost, etc. | ||