Basic Testing Procedure

Below is a testing procedure cobbled together from the last few bug fixes. To be clear, THIS IS NOT A FULL-BLOWN TESTING METHODOLOGY. This is just something developers can do on their own to avoid checking easily catchable mistakes.

The problem list below is not a comprehensive test suite for Astro BEAR2.0, nor even necessarily a simple test suite. It is, however, a good basis from which to build a quick-and-dirty suite that will enable us to get AstroBEAR 2.0 out the door.

Checking Code Into Central Repository

1. Clone a clean copy of your code from your working repository onto bluehive or some other production machine:

hg clone ssh://username@grass.pas.rochester.edu//home/username/working_repo clean_repo

2. Use the code in clean_repo to perform the following tests:
   1. 3D field loop
      1. 1, 8, 16 processors, MaxLevel 0.
      2. 1, 8, 16 processors, MaxLevel 2.
      3. 8 processor restart, MaxLevel 2.
   2. 3D orbiting particles
      1. 1, 8, 16 processors, MaxLevel 0.
      2. 1, 8, 16 processors, MaxLevel 2.
      3. 8 processor restart, MaxLevel 2.

3. Check your code into scrambler_devel on clover. Note the ID of the Mercurial changeset before your checkin.

4. Send a notice to the rest of the team that you have checked code into the central repository. Be sure to include the following:
   1. A description of your changes.
   2. A list of the tests you've run.

Checking Ticketed Bug Fixes Into Central Repository

1. Follow steps 1-2 from "Checking Code Into Central Repository" (see above).

2. Use the code in clean_repo to perform the following tests on the simulation you are debugging (the one referenced in the bug ticket):
   1. 1, 8, 16 processors, MaxLevel 0.
   2. 1, 8, 16 processors, MaxLevel 2.
   3. 8 processor restart, MaxLevel 2.

3. If possible, announce the bug fix on the trouble ticket and have the bug reporter try it out before checking the fix in.

4. Check the fix into the central repository.

5. Post a notice on the trouble ticket that the fix is available, and is in the central repository. Be sure to include the following:
   1. A description of your changes.
   2. The bug ticket number.
   3. A list of the tests you've run.

6. Close the ticket.