Test Plan Details
Assignment 3 CISC 323, Winter 2006
Queen's University, Kingston, Ontario

Your test plan should consist of a list of tests. For each test, include the following:

  1. A name or number for the test, so that other tests may refer to it
  2. The purpose of the test: what you are testing and why.
  3. Input data required
  4. Expected output (oracle)
  5. Detailed steps the tester is to follow, eg. push this button, enter this value in this box, call up report, check report to make sure exposure value for Worf is XXX BTUs, etc. It may be easier in some cases to embed the required input and expected output in the detailed instructions. Use whatever format works best. However, make sure it is clear what is input and what is expected output. Note that the test steps are tied to your particular design. By thinking about a detailed test plan during design, you will be thinking about testability of your design.
You should realize that the number of possible tests even for this small part of CorTrap is huge. You may want to think first about the types of tests you want run, design those tests at a higher level, then give instructions such as: repeat the following test for eg., the following numbers, eg., for samples in the following range of numbers, etc. When you start thinking this way, you are actually starting to think of test design. This can be as intense as designing the software itself.

You may also want to think about the interaction of tests. For example, what if I do this, then this, then this … Again, the number of tests can explode. Your test design should be a set of simple tests, then instructions on how to do multiple combinations of these tests. Assume the Tofos love testing and will test till they drop!