For each releases, alpha testers should do

1. The platform-independent tests
2. As many of the other test groups as possible.

Platform-independent tests

Tests to do on all platforms.

• Upgrade install: Note fraction done of existing results. Install BOINC on top of existing install. Make sure results resume with same fraction done. Make sure graphics work (for all apps that support graphics). Make sure CPU time and fraction done are increasing for running apps.
• Check all tabs in BOINC manager, make sure data is there.
• Result completion: Let BOINC run long enough to complete a result. Verify that output file is uploaded, that the result is reported, and that new work is downloaded and started.
• Suspend/resume features: suspend and resume results, file transfers, and projects.
• Download restart: Exit BOINC in the middle of a long file download. Note the fraction done. Restart BOINC. Verify that download resumes from the same point.
• Test activity modes 'suspended', 'based on preferences', 'always'.
• Test 'don't run when user active' preference.
• Test 'leave applications in memory' preference.
• Test scheduling period preference.
• Test #processors preference.
• Test 'use network between hours' preference.

Windows single-user

• Check to make sure that only the administrative and installing account can and view the BOINC directory.

Windows multi-user

• Everyone should be able to view the directory. Anybody should be able to execute the manager but only the first person who executed the manager should have started a core client process.

Windows service mode

• Use of 'net start boinc' and 'net stop boinc' on the command line should start and stop the core client.
• Use of 'net pause boinc' and 'net continue boinc' should pause and resume the core client.
• The core client should be started when the machine boots up.
• the core client should continue processing when nobody is logged onto the system.
• Manager should be able to communicate with the core client without issue.

Mac OS X

Linux/x86 graphical

Linux/x86 command-line

Tests for modem-connected computers

• Test 'confirm before connect' preference.
• Test 'Disconnect when done' preference.
• Test processing only when idle.

Tests for computers connected by HTTP proxy

• Check HTTP proxy if you have one.

Tests for computers connected by SOCKS proxy

• Check SOCKS proxy if you have one.

Tests for computers connected by HTTP proxy with authentication

• Check HTTP Authentication if you use authentication. (basic, digest, NTLM, Negotiate, kerberos)

Tests for computers connected by SOCKS proxy with authentication

• Check SOCKS Authentication if you use authentication.

Tests for laptops

• Test 'work while running on batteries' preference'

Screensaver tests (Windows, Mac)

• Test normal case
• Test change apps (set scheduling period to 1 min)
• Test 'no graphics capable apps'
• Test blank time
• Test power save modes

BOINC Manager wizard tests

• Test normal case, invalid urls, valid urls, projects that are up, projects that are down.
• Test good passwords, bad password, good usernames, bad usernames.
• Test existing accounts, create new accounts.
• Test against projects that don't support usernames and passwords.

Advanced tests

Optional tests.

• Clean install: Uninstall BOINC. Remove BOINC directory. Install new BOINC. Verify that manager starts, asks for project info.
• Try to connect to core client with bad password, from host not on list, etc.
• (Unix) Try to overwrite executable file logged in as different user.
• Test 'do work between hours' preference.
• Test venue mechanism