|
|
| Line 1: |
Line 1: |
| Last summer the intial beta was coded in java by a gsoc student. We would like to extend the current beta into a more robust and functional app that we can deploy into the field. | | Last summer the intial beta was coded in java by a gsoc student. We would like to extend the current beta into a more robust and functional app that we can deploy into the field. |
|
| |
| Some examples of the tests we run currently that we would like to have in the new version of the tool are:
| |
|
| |
| *Information on the client the test is being run from
| |
| ** IP
| |
| ** ISP
| |
| ** OS version
| |
| *Network routes to specific internet hosts
| |
| *Speed tests to specific internet hosts
| |
| *Filtering tests for specific blocked ports
| |
| *Filtering tests to specific internet hosts
| |
|
| |
| We're looking to build the next-generation of a tool that would do the same, except be web-centric.
| |
|
| |
| Some of the features we are looking to include in this tool:
| |
|
| |
| *Easy for users to run in various countries
| |
| **Possible multi-language integration
| |
| **Autodetection of location and ability to run different test suites
| |
| *Easy to update
| |
| **Both in the aspect of the code itself
| |
| **but more importantly in the tests that are run - researchers should have the ability to add and modify tests
| |
|
| |
| Are there more tests you think you would like to include? Ideas?
| |
Latest revision as of 20:38, 8 March 2011
Last summer the intial beta was coded in java by a gsoc student. We would like to extend the current beta into a more robust and functional app that we can deploy into the field.