Auto-tools/Projects/SpeedTests: Difference between revisions

Auto-tools/Projects/SpeedTests (view source)

1,279 bytes added , 29 September 2011

Confirmed users

1,927

edits

@@ Line 75: / Line 75: @@
 Note that it is ''unnecessary'' to update Nightly, since the client automatically downloads the latest version.
+=== Setting up browser profiles ===
+This is the trickiest part.  The framework needs relatively clean profiles with nothing cached, with popups enabled for the test server (since tests are opened in a separate window to control the size), and with access to localhost permitted (only an issue with Opera, I believe).  There are also other random things that need to be dismissed, like add-on compatibility dialogs.
+At the moment, I start a test run with --testmode.  This will verify most of the settings without having to sit through all the tests.  If I see a browser not being able to load a test, I stop the controller, set all the correct permissions, clear the cache, and run <tt>python speedtests.py archive &lt;browser name&gt;</tt>, where <tt>&lt;browser name&gt;</tt> is one of <tt>firefox</tt>, <tt>nightly</tt>, <tt>safari</tt>, <tt>"internet explorer"</tt>, or <tt>chrome</tt>.  To retest this browser, I start the tests again in testmode, providing the browser name.
+If something funny is still happening, you can run with --noresults, which will execute the full tests but not report results back to the server, so you don't have to worry about affecting the results with VNC open (VNC is *supposed* to not interfere with framerates, but I have my doubts...).
 == Major Tasks Remaining ==