The UI (we are at v1 now, v2 will probably be that which satisfies the City's requirement) for, say, v3 should have the ability to run tests on a schedule.
A user pulls down seanette, and can leave it running. Seanette will run a test on a regular basis and chart it but only locally, without central record. These results can be archived on a server is a user chooses to do so. Such a server (and, again, this is not the City of Seattle's initial deploy) can register users and accumulate tests over time for a user.
The UI (we are at v1 now, v2 will probably be that which satisfies the City's requirement) for, say, v3 should have the ability to run tests on a schedule.
A user pulls down seanette, and can leave it running. Seanette will run a test on a regular basis and chart it but only locally, without central record. These results can be archived on a server is a user chooses to do so. Such a server (and, again, this is not the City of Seattle's initial deploy) can register users and accumulate tests over time for a user.