| 1 | [[PageOutline]] |
| 2 | = BOINC server software testing = |
| 3 | |
| 4 | We rely on volunteers to test the BOINC server software. |
| 5 | The server software includes everything used by projects: |
| 6 | |
| 7 | * The scheduler, feeder, transitioner, and so on. |
| 8 | * The API code |
| 9 | * Wrappers |
| 10 | * The PHP web code |
| 11 | * The python scripts are creating and controlling projects |
| 12 | |
| 13 | == Becoming a Server tester == |
| 14 | |
| 15 | When we are preparing to release a new version of the server software, |
| 16 | testers are expected to |
| 17 | |
| 18 | * Download the software under test, |
| 19 | and install it on a new or existing project. |
| 20 | Established BOINC projects can use a separate test project for this purpose. |
| 21 | * Build applications and deploy them on the test project. |
| 22 | * Carefully monitor the test project |
| 23 | * Report the results of testing |
| 24 | |
| 25 | If you are OK with this and want to help test BOINC, |
| 26 | send email to [ProjectPeople David Anderson], |
| 27 | and we'll give you an account in the BOINC server test project. |
| 28 | |
| 29 | Testers must subscribe to the [mlist:boinc_dev boinc_dev email list]. |
| 30 | (You don't need to be a tester to subscribe to this list). |
| 31 | |
| 32 | == How to test == |
| 33 | |
| 34 | See [http://isaac.ssl.berkeley.edu/alpha/server_test_matrix.php the set of test cases]. |
| 35 | For each release, please do all the General tests, |
| 36 | and as many of the other tests as your time and computer environment permit. |
| 37 | |
| 38 | If you experienced problems with BOINC that are not covered by any of these tests, |
| 39 | please post to the [mlist:boinc_dev boinc_dev@ssl.berkeley.edu email list]. |
| 40 | |
| 41 | == How to report test results == |
| 42 | |
| 43 | Report results through the [http://isaac.ssl.berkeley.edu/alpha/server_test_form.php web-based interface]. |
| 44 | You must log in to the [http://isaac.ssl.berkeley.edu/alpha/ BOINC Alpha project] |
| 45 | to report test results. |
| 46 | |
| 47 | == How to report bugs == |
| 48 | |
| 49 | In addition to reporting negative test results, we strongly encourage you to |
| 50 | [ReportBugs submit detailed bug reports]. |
| 51 | |
| 52 | If you're not sure whether something is a problem, post to the boinc_dev@ssl.berkeley.edu email list. |