Confirmed users
1,927
edits
Auto-tools/Projects/SpeedTests: Difference between revisions
Jump to navigation
Jump to search
Auto-tools/Projects/SpeedTests (view source)
Revision as of 20:39, 26 September 2011
, 26 September 2011Maintenance section
(Maintenance section) |
|||
| Line 54: | Line 54: | ||
* load <browser>: Starts <browser> with the currently stored profile | * load <browser>: Starts <browser> with the currently stored profile | ||
== | == Client Maintenance == | ||
We limit network access on the machine in order to prevent browser and system updates, which might throw off results if a test is running at the same time. Unfortunately this requires periodic manual maintenance in order to install desired updates (e.g. to test against recent browser releases), but it should be minimal. | |||
Network access is limited by setting the DNS server to localhost, i.e. an invalid host. Thus all DNS lookups, except those in the hosts file, will fail, preventing the majority of Internet access. There's a helper program distributed with the client called <tt>nw.py</tt> that can be used to disable and re-enable DNS. | |||
This is the process for updating a SpeedTest client: | |||
# Open a terminal as administrator. | |||
# Go to the speedtests client directory (generally /Users/mozilla/speedtests/client). | |||
# Run <tt>python nw.py enable</tt> to enable full network access. | |||
# Run Firefox, Chrome, and Opera, checking each for updates. | |||
# Run the Apple Updater to look for Safari updates (don't install other software like Quicktime!). | |||
# Run Windows Update. | |||
# Run Windows Update again to see if there are subsequent updates. | |||
# Run <tt>python nw.py disable</tt> to disable full network access. | |||
# Reboot. | |||
== Major Tasks Remaining == | == Major Tasks Remaining == | ||