1. The general tests
2. As many of the other test groups as possible.

General tests

• Note fraction done of existing results. Install the new version on top of an older version. Make sure BOINC client and manager start up. 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.
• Detach from a project (e.g., alpha test) and reattach. Make sure new work gets downloaded.
• 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.
• Exit BOINC in the middle of a long file download. Note the fraction done. Restart BOINC. Verify that download resumes from the same point.
• Suspend/resume features: suspend and resume results, file transfers, and projects.
• Test activity modes 'suspended', 'based on preferences', 'always'.
• Shut down your computer and reboot it. Make sure client and manager start up OK.

Clean install

• Uninstall BOINC.
• Remove BOINC directory.
• Install new BOINC.
• Verify that client and manager run, and manager brings up the Attach Project wizard.
• Attach to a project (e.g. alpha) and make sure work is downloaded and started.

Preferences tests

• 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.
• Test 'do work between hours' preference.
• Test venue mechanism

Windows single-user

• Check that only the administrative and installing account can control the core client (via the BOINC manager) 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.

Tests for modem-connected computers

• Do General Tests from a modem-connected computer.
• Test 'confirm before connect' preference.
• Test 'Disconnect when done' preference.

Tests for computers with personal firewalls