The purpose of test planning 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.<\/p>\n\n\n\n
The test plan is an ongoing document, particularly in the spiral environment since the system is constantly changing. As the system changes, so does it. A good test plan is one which:<\/p>\n\n\n\n
\u2022 Has a good chance of detecting a majority of the defects
\u2022 Provides test coverage for most of the code
\u2022 Is flexible
\u2022 Is executed easily, repeatably, and automatically
\u2022 Defines the types of tests to be performed
\u2022 Clearly documents the expected results
\u2022 Provides for defect reconciliation when a defect is discovered
\u2022 Clearly defines the test objectives
\u2022 Clarifies the test strategy
\u2022 Clearly defines the test exit criteria
\u2022 Is not redundant
\u2022 Identifies the risks
\u2022 Documents the test requirements
\u2022 Defines the test deliverables<\/p>\n\n\n\n