CONTENTS
Where is the database?
BUG REPORTING
BUG FIXING
TEST REQUESTING
TEST COMPLETION
MANAGEMENT BY GUILT
What about PlanIt?
Z:\software_testing.mdb
...where you have bound the Z: drive to be \users on DREAM.
It's an access database. I suggest you put a shortcut to it on your desktop.
...is pretty self-explanatory. Just add a new record to the Miner Bugs database.
You should periodically check the database to see if there are any unfixed bugs for which you are the suggested fixer. When you do so, you can have the exquisite joy of clicking the "fixed" checkmark.
When you add a new command, or do a major update of a command, or do some other piece of major changing you should do two things:
(1) Add a new component to the testing script that excercises your new command. See the email that Paul is about to send us all with detailed instructions on how to do that.
(2) Add a new record to the Testing Tasks table, in which you RANDOMLY UNIFORMLY GENERATE the tester by rolling a five sided dice (the tab in cells in the tester column will show you who the available testers are). Notice that your command should be sufficiently well documented using the Miner Help System that the tester will know what to do in order to do the testing.
TEST COMPLETION
If you are an assigned tester (you must periodically check the database
to see if you are) you should do the testing task, and when you've
played with the command, seen that it works and understood it, then
click the TESTED check mark in the Testing Tasks table.
Each week before the Tuesday lunch meeting the Testing Tasks and Miner Bugs tables will be printed out, and the roll of shame (those who have not completed their bug-fixing or testing tasks) will be solemnly announced.
A new PlanIt Bugs sections will be added by the first person who finds a Planit bug in the same database.
But Planit and Miner should share the same Testing Tasks database as it is a Good Thing for PlanIt engineers to test Miner Code and vice versa.