Checklist: Test Plan
This checklist helps make sure that a Test Plan is complete.
Relationships
Related Elements
Check Items
The scope of the test effort is clearly identified

It must state the following:

  • Stages and types of test to be implemented and executed
  • Target-of-test features or functions to be tested / not tested (if appropriate)
  • Any assumptions, risks, or contingencies which may affect or impact the test effort
The artifacts used to generate the test plan are clearly identified
Version information should be included.
Each project requirement has at least one associated requirement for test or justification

If there is no associated test requirement, then a statement should be included that justifies why it is not a requirement for test

All the requirements for test have been identified and prioritized
Each of the different types of tests to be implemented and executed should be identified and prioritized.
A clear and concise test strategy is documented for each type of test
For each test strategy, has the following information has been clearly stated:
  • The name of the test and its objective
  • A description of how the test will be implemented and executed
  • A description of the metrics, measurement methods, and criteria to be used evaluate the quality of the target-of-test and completion of the test
All the resources needed have been identified
This includes hardware, software, and personnel.
Schedule or list of milestones identifies the major project and test related tasks
Start and end dates, and / or effort should be included.
The artifacts created by the test tasks are documented
This includes identifying the artifacts, documenting when the artifacts are made available, how they will be distributed, their content, and how they should be used.