STEP 11. TEST PLAN
Table of Contents
TEST PLAN INSTRUCTIONS
Enter the title of the project.
1.1 Project Objectives
Briefly describe the business objectives of the system being tested.
Briefly describe the system and the functions it is intended to perform.
Briefly describe the objectives of the Test Plan; e.g., defining responsibilities, identifying test methodologies and phases, identifying the test environment, etc. Explain how the plan might evolve throughout the project lifecycle.
Identify any sources of information used to develop this plan. Include documents which define and trace the system requirements to be tested; e.g., a Requirements Document.
State any project planning issues or problems relevant to testing which are known as of this plan revision. Describe the effects of such issues on test planning.
2.1 Features to be Tested
Specify all features and combinations of features to be tested. This could include items such as user manuals or system documents.
Specify all features and significant combinations of features not to be tested. Explain the reasons for excluding these features from testing.
3.1 Testing Approach
For each major group of features or feature combinations, specify the types of tests required; e.g., regression, stress tests, pilot tests, etc. Specify the major activities, techniques, and tools to be used to test the designated features.
3.1 Testing Data
3.1 Testing Data
Provide a general description of the sources of test data. Describe how the range of test data will help to ensure the adequacy of testing; e.g., selection of boundary or null values.
Identify test documents that are created throughout the project lifecycle. Include more specific documents, such as test cases, acceptance test plans, integration test reports, etc.
Explain how tests and test results will be mapped to documented system requirements. Describe the procedure for ensuring that requirements are validated.
Describe the procedure for identifying, recording, and tracking test results to closure. Document the change control procedure.
4.0 TEST PHASES
Identify test phases, such as unit, integration, system acceptance, and prototype testing. For each phase address the topics described below.
Provide a brief explanation of the process the (scenario) involved in performing the activities in the phase.
Identify the person or group responsible for conducting this test phase. Describe the expected level of involvement of the project team, test group, and any other functional areas.
Provide a more detailed description of the source and type of data for this test phase.
Specify the entrance and exit criteria for this phase. Describe how test results are evaluated. Explain the criteria for test sufficiency.
Identify requirements to be validated in this phase.
Describe the software work products which are initiated and/or completed in this phase, including test documents and reports.
Describe the hardware requirements for the test environment. Include a description of networks.
Describe the software requirements for the test.
Outline the office and space requirements for the test environment. Identify all sites where testing occurs.
Identify any staffing or training needs.
Provide a detailed schedule of testing activities and responsibilities. Indicate dependencies and time frames for testing activities. A Gantt Chart is desirable.
Include an appropriate SC concurrence/approval section.
Provide a glossary of all technical terminology used within the document.
Use appendices to document any specific alternative vendor information.