| 1 | = Managing the Alpha test system = |
| 2 | |
| 3 | We need to test the client software on a wide range of platforms, |
| 4 | OS versions, and hardware and software configurations. |
| 5 | To do this we use volunteers called "Alpha testers", |
| 6 | who run test versions of the client software and report results through a web interface. |
| 7 | The web site, https://boinc.berkeley.edu/alpha/, |
| 8 | also lets you view test results. |
| 9 | |
| 10 | The file boinc_alpha/test.inc (in isaac) lets you configure testing. |
| 11 | At the top there is a list of platform (HW/OS version combos) |
| 12 | with a "target number" of test results for each. |
| 13 | More popular platforms have higher targets; |
| 14 | adjust these numbers based on the number of results you're getting. |
| 15 | |
| 16 | There follows a list of tests |
| 17 | |
| 18 | $versions is a list of versions to test. |
| 19 | To add a new version, put it at the top of the list. |
| 20 | Following the version number is the set of tests to do, and the set of platforms to cover. |
| 21 | |
| 22 | When you start a testing cycle, use all tests and all platforms. |
| 23 | As bugs get fixed and you do sub-release testing, |
| 24 | you can limit the tests and platforms as needed. |
| 25 | |
| 26 | Some tests (like transfer_restart) need to be done only when libcurl is updated, |
| 27 | and are disabled by default. |
| 28 | Enable them as needed. |
| 29 | |
| 30 | == Communicating with Alpha testers == |
| 31 | |
| 32 | Communicate with Alpha testers via the boinc_alpha email list: |
| 33 | http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_alpha |
| 34 | |
| 35 | Send emails when: |
| 36 | |
| 37 | * a test cycle or subcycle starts or ends. |
| 38 | Tell them exactly what's new and different about each test release. |
| 39 | When a cycle is done, thank them for their effort. |
| 40 | * more results are needed for a particular platform. |
| 41 | * Major bugs are identified or fixed. |
| 42 | |
| 43 | == Recruiting Alpha testers == |
| 44 | |
| 45 | If you're not getting enough test results, |
| 46 | recruit testers on the BOINC or SETI@home message boards. |
| 47 | |
| 48 | Testers register by sending email to an admin (currently David A.). |
| 49 | The admin creates an account on the Alpha project on isaac, |
| 50 | and sends them the account password and link to testing instructions. |