Confirmed users
1,927
edits
Auto-tools/Projects/SpeedTests: Difference between revisions
Auto-tools/Projects/SpeedTests (view source)
Revision as of 22:05, 29 September 2011
, 29 September 2011→Architecture
| Line 15: | Line 15: | ||
The tests use a common set of JavaScript functions to collect and report results. The browser controller collects results from each browser and forwards them onto the results server (the latter can be disabled for local testing). When the last browser has executed the last test, the controller shuts down its HTTP server, prints a report to stdout, and exits. | The tests use a common set of JavaScript functions to collect and report results. The browser controller collects results from each browser and forwards them onto the results server (the latter can be disabled for local testing). When the last browser has executed the last test, the controller shuts down its HTTP server, prints a report to stdout, and exits. | ||
The test server can be the same server as the results server, or it can be separate. In the current setup, they are separated, with the test server running | The test server can be the same server as the results server, or it can be separate. In the current setup, they are separated, with the test server running on the internal network, since we can't distribute the modified tests. It is the test server that also serves up the JS library for reporting results. | ||
The location of the test and result servers is configured in an ini file on the client. | The location of the test and result servers is configured in an ini file on the client. | ||