6. Test Plan
In an ideal world a test plan will have been written during the design stage. However, sometimes the test plan gets left until now.
The test plan is a detailed document which a team of testers must follow carefully. It will set out every single test they are to do on the system, what data they should enter and what result they should expect to obtain.
For example one test might look something like this:
Test no. |
Part of system |
What is being tested |
Test data |
Expected result | Actual result | Pass / Fail |
23 |
Customer input form |
Input mask on postcode to check that numbers cannot be entered where letters should be. |
45CV523 |
Fail - should not be able to enter postcode |
|
|
The first five columns are already completed in the test plan. The final two columns are left blank for the testers to complete when they do the test on the system.
The test plan should ensure that the testing covers:
- the requirements of the system
- the performance of the system against the original design
- pathways through the system
- validation routines
challenge see if you can find out one extra fact on this topic that we haven't already told you
Click on this link: Test Plan