Testing Plans

Testing is a crucial part of development. It should be incorporated from the beginning.

One way to set up a test plan is to look at the use cases. Your product should meet the requirements of each use case. Each use case should be tested systematically. One approach is to list each use case and the expected result from running the program. Run the program and check to see if the actual result is the same as the expected result. If it is, good. If not figure out why. Document any changes and test again.

You should test for exceptions as well as valid results. What happens if bad data is entered? What happens if a file is missing, or a database connection fails?

Thoroughly testing code is the only way to guarantee basic quality.


Here is a picture of a simple testing plan for the core use case of the card reader app.