Test matrix

For each release, please do

The general Tests.
As many of the other test groups as possible.

If you have experienced problems with BOINC that are not exercised by any of these tests, please post to the boinc_alpha@ssl.berkeley.edu email list.

General tests

Note fraction done of existing tasks. Install the new version on top of an older version. Check that BOINC client and manager start up and tasks 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 task. Verify that output file is uploaded, that the task is reported, and that new work is downloaded and started.
Suspend and resume tasks, 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.
Suspend and/or hibernate your computer, and resume it. Make sure client and manager resume OK.
If anything seems significantly slower as a result of BOINC, report it as a minor bug.
Check that the 'Help' menu items bring up a web browser and loads a Help page on the BOINC site.
Windows only: Verify that pressing 'F1' brings up a web browser and loads a Help page on the BOINC site.

Clean install

This test may cause you lose work in progress; do it only if you know what you're doing.

Remove BOINC (Windows: go control panel -> add/remove programs and uninstall BOINC). Then rename the BOINC data directory to a temporary name.
Install new BOINC.
Verify that client and manager run, and manager brings up the Attach Project wizard.
Attach to SETI@home or other projects, and make sure work is downloaded and started.
There should be no long delays, errors, confusing messages, or anything else that might bother a naive, non-technical computer user. If there is, report it as a a bug.
Detach from SETI@home or other projects.
Exit BOINC, delete the BOINC data directory, and rename temporary directory back to BOINC.
Reinstall BOINC.

File transfer restart

In the middle of a long file download, note the fraction done, then exit the BOINC client (e.g., using 'Advanced/Shut down connected client' in the Manager). Restart the client by exiting and launching the Manager. Verify that the download resumes from the same point. Use the BOINC Alpha project for this.
Same, but instead of exiting the client, disconnect your network cable in the middle of the transfer.
Same as above two, but upload instead of download.

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 'CPU usage limit' preference.
Test RAM usage limit preferences (both of them).
Test venue mechanism (e.g., create preferences for 'Home', change your computer's location to 'Home', make sure it gets the right preferences).
Update a second project with same account email address, and make sure preferences are propagated to the second project.

These tests can be done by changing preferences on web site, then Updating the project in the BOINC manager.

Windows compatibility/private install tests

This install mode is selected by unchecking the 'Protected application execution' checkbox and checking the 'All users can control BOINC' checkbox on the advanced configuration screen.

Launch BOINC Manager and verify that the client runs and you can control it.
Launch Task Manager (CTRL-SHIFT-ESC), switch to the 'Processes' tab and verify that boinc.exe, boincmgr.exe, and any science applications are running as the current user account.
Log on as a different user and launch BOINC Manager. A dialog should appear telling you to contact an administrator and have them add you to the 'boinc_users' group.

Windows secure/private install tests

This install mode is selected by checking the 'Protected application execution' checkbox and unchecking the 'All users can control BOINC' checkbox on the advanced configuration screen.

Launch BOINC Manager and verify that the client runs and you can control it.
Launch Task Manager (CTRL-SHIFT-ESC), switch to the 'Processes' tab and verify:
- boinc.exe is running as 'boinc_master'.
- boincmgr.exe is running as the current user.
- science applications are running as 'boinc_project'.
Log on as a different user and launch BOINC Manager. A dialog should appear telling you to contact an administrator and have them add you to the 'boinc_users' group.

Windows secure/public install tests

This install mode is selected by checking the 'Protected application execution' checkbox and checking the 'All users can control BOINC' checkbox on the advanced configuration screen.

Launch BOINC Manager and verify that the client runs and you can control it.
Launch Task Manager (CTRL-SHIFT-ESC), switch to the 'Processes' tab and verify:
- boinc.exe is running as 'boinc_master'.
- boincmgr.exe is running as the current user.
- science applications are running as 'boinc_project'.
Log on as a different user and launch BOINC Manager. You should be able to attach to projects, suspend/resume work, etc.

Windows data migration tests

During installation, choose a new data directory to migrate BOINC's data files to.

After installation check to see that your data files were moved to the new directory and that both BOINC and BOINC Manager launch and can use the data files.

Tests for modem-connected connections

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 'CPU usage limit' preference.
Test RAM usage limit preferences (both of them).
Test venue mechanism (e.g., create preferences for 'Home', change your computer's location to 'Home', make sure it gets the right preferences).
Update a second project with same account email address, and make sure preferences are propagated to the second project.
These tests can be done by changing preferences on web site, then Updating the project in the BOINC manager.

Tests for computers with personal firewalls

Do the General Tests on a computer that uses a personal firewall (ZoneAlarm, Symantec, Windows XP, etc.). In your test report Comments field, indicate the type of personal firewall.

Tests for computers connected by HTTP proxy

Do the General Tests on a computer connected via an HTTP proxy.
Use authentication if possible.
Advanced test: Configure BOINC so that attempting to connect to a different local computer is excluded from using the proxy. Enable logging flag. Verify that an attempt to attach to a fake project on the excluded computer does in fact skip using the proxy server.

Tests for computers connected by SOCKS proxy

Do the General Tests on a computer connected via a SOCKS proxy.
Use authentication if possible.
Advanced test: Configure BOINC so that attempting to connect to a different local computer is excluded from using the proxy. Enable logging flag. Verify that an attempt to attach to a fake project on the excluded computer does in fact skip using the proxy server.

Tests for laptops

Test 'work while running on batteries' preference.

Screensaver tests

Test normal case (enter/leave screensaver mode).
Open graphics windows from Manager before enter/leave screensaver; make sure they reappear.
Graphics change on CPU reschedule (set scheduling period to 1 min).
Test 'no graphics capable apps'.
Test 'blank screen after X minutes'.
Test power-saver modes, e.g. 'turn off monitor after N minutes'.
Test password-after-resume options.
Test screensaver properties 'Preview' function.
(Windows only?) Test multi-user install - switch to different user and run screensaver.

BOINC Manager 'Attach to Project' tests

Test normal case, invalid URL, valid but non-BOINC URL, projects that are down.
Test bad password, bad username.

GUI RPC authentication

Try to connect to core client with bad password, from host not on list, etc.

Account manager functions

Attach to and detach from an account manager such as GridRepublic or BOINCStats.
Verify that the core client periodically synchronizes with the account manager.
Verify that the core client won't let you detach from a project that you attached via the account manager.
Create a new account on GridRepublic, click download link, abort download, then install new custom client. It should attach automatically.

NOTE: If you find bugs in the account manager itself, report them directly to the account manager admins, not to BOINC Alpha.

Trickle messages and intermediate file upload

Let CPDN run long enough so that it does a trickle-up request and an intermediate file upload. Make sure that these succeed.

CUDA tests

(This test applies only if your computer has an NVIDIA GPU.)

Check here to see if your GPU is CUDA-capable.
If it is, download and install the latest CUDA driver (you don't need the toolkit or SDK).
Attach to a project that has a CUDA application (currently there is only one such project: GPUgrid).
Verify that CUDA jobs are downloaded and executed. BOINC should keep your GPU (or GPUs, if you have more than one) busy all the time.

Notes:

CUDA won't work on Vista if you chose the 'protected application execution' install option. If this applies to you, either skip this test or reinstall BOINC without this option.
Skip this test if you're on a Macintosh; BOINC doesn't support CUDA yet on Mac.

ATI GPU tests

(This test applies only if your computer has an ATI GPU.)

Check here to see if your GPU is Stream-capable.
If it is, download and install the latest CAL driver.
Attach to a project that has a CAL application (currently there is only one such project: Milkyway).
Verify that CAL jobs are downloaded and executed. BOINC should keep your GPU (or GPUs, if you have more than one) busy all the time.

Notes:

CAL/Brook+ won't work on Vista if you chose the 'protected application execution' install option. If this applies to you, either skip this test or reinstall BOINC without this option.

Configuration tests

Add an 'exclusive application' to cc_config.xml. For example:
```
<cc_config>
   <options>
      <exclusive_app>notepad.exe</exclusive_app>
   </options>
   ...
</cc_config>
        
```
Verify that when you launch that application (Notepad in this case), BOINC suspends tasks.

BOINC Manager tests

Check all the tabs.
Switch between the Simple GUI and Advanced GUI.
Check that translation is working: in Advanced/Options/General, select a non-English language, restart the Manager, and check that text is shown in that language.
In the Projects tab, select a project and click Properties; check that a dialog appears showing correct project info.
Same thing, for Task Properties.

BOINC Manager Exit tests

Verify that the shutdown option shuts down the core client.
Verify that the remember this choice feature works for future exits.
Re-enable display the exit dialog by going to the advanced view and selecting Advanced/Options from the menu.

BOINC Manager Terms of Use tests

Verify that the terms of use wizard page appears for the alpha project.