A Test Specification describes test objectives and approach. It also
contains a requirements coverage matrix showing every requirement the
software system is to meet versus specific, numbered test cases designed
to validate that the system meets those requirements. For any given
system requirement, or function, it should be easy to locate in this
matrix all relevant test cases. If you have trouble writing this matrix,
you may have a fuzzy set of tests.
The foundation for your Test Specification is the combination of the
Problem Specification and the Design Specification. From the Problem
Specification, you should be able to envision tests that will
demonstrate that the system does what it was supposed to. From the
Design Specification, you should be able to identify the more complex
areas of the programs- and this is where defects are most likely to be
found.
Each test case consists of a script, data, and checklists.
Go to...
Script | Data |
Checklist
|
