Auto-tools/Projects/SpeedTests: Difference between revisions

Conceptually the system can be split into three parts, the browser controller, the report and test server, and the tests themselves.  However they are best understood by looking at the whole process rather than the individual parts.

The browser controller has a list of browsers likely to be installed on the target platform.  It iterates through the list, executing the browser if it is found, pointing it to the server path /nexttest/, which replies with a redirect to the first test (in string order).  It also has a simple HTTP server running on a special port, which awaits a callback from the browser when the last test has executed.

The tests use a common set of JavaScript functions to report results and to load the next test.  The server collects results and serves tests.  When the test is finished, the browser sends the results via XHR and then loads the URL /nexttest/<current test name>, eg. /nexttest/PsychedelicBrowsing/, which redirects to the test that, in string order, follows the current test.  If the current test was the last test, the server redirects the browser to the callback port on the localhost.

Upon receiving a GET request on the callback port, the browser controller terminates the current browser and launches the next one in the list.  When the last browser has executed the tests, the controller shuts down its HTTP server and exits.