Instructions for alpha testers
Becoming an alpha tester
The BOINC testing program helps us find and fix bugs in the BOINC software before we release it to the public. Testing is vital to the success of BOINC. If you're a tester, then:
- You'll need to spend about 1 hour per week doing testing;
- You'll run experimental versions of BOINC that may crash or cause jobs to fail.
- You may be asked to assist, via phone or email, in troubleshooting.
If you are OK with all this and want to help test BOINC, send email to David Anderson or Rom Walton, and we'll give you an account in the BOINC Alpha test project (this is a BOINC project but it never has jobs; don't attach your client to it).
Testers must subscribe to the boinc_alpha email list. (You don't need to be a tester to subscribe to this list).
When to test
Periodically (every couple of weeks, sometimes more) we'll send an announcement on the email list, asking alpha testers to download and test a specific new release of BOINC. You can find these releases on the BOINC download page. Please try to report test results within 3-4 days of receiving the email.
How to test
See the set of test cases. For each release, please try to do all the General tests. Please try to do as many of the other tests as your time and computer environment permit.
If you experienced problems with BOINC that are not exercised by any of these tests, please post to the email@example.com email list.
The client software under test may have bugs that wipe out tasks in progress, so consider using a different data directory when you install the test software.
How to report test results
How to report bugs
In addition to reporting negative test results, we strongly encourage you to submit detailed bug reports.
If you're not sure whether something is a problem, post to the boinc_alpha@… email list.
Windows users: if you have install/uninstall problems, you may need to use the Windows Installer CleanUp Utility