ABSTRACT
The purpose of the test project plan is to provide the basis for accomplishing testing in an organized manner. From a managerial point of view it is the most important document, because it helps manage the test project. If a test plan is comprehensive and carefully thought out, test execution and analysis should proceed smoothly. (See Appendix E1 for a sample unit test plan, Appendix E4 for a sample system test plan, and Appendix F24, which can be used to verify that unit testing has been thorough and comprehensive.)
The test project plan is an ongoing document, particularly in the spiral environment because the system is constantly changing. As the system changes, so does it. A good test plan is one that:
• Has a good chance of detecting a majority of the defects • Provides test coverage for most of the code • Is flexible • Is executed easily and automatically and is repeatable • Defines the types of tests to be performed • Clearly documents the expected results • Provides for defect reconciliation when a defect is discovered • Clearly defines the test objectives • Clarifies the test strategy • Clearly defines the test exit criteria • Is not redundant • Identifies the risks • Documents the test requirements • Defines the test deliverables
Although there are many ways a test plan can be created, Exhibit 12.1 provides a framework that includes most of the essential planning considerations. It can be treated as a checklist of test items to consider. Some of the items, such as defining the test requirements and test team, are obviously required, however, others may not be. It depends on the nature of the project and the time constraints.
