Sample Test Plan
This section should contain a summary of the product that is being tested. A very general outline of how the product functions should be included.
This section describes the functions of the product that is being tested, the existing interfaces, etc. An overview of the procedures and processes that will be followed to verify these functions should also be included.
3.0 FUNCTIONS INCLUDED IN TESTING
This section should identify all of the software functions and/or combination of functions that will be tested.
4.0 FUNCTIONS EXCLUDED FROM TESTING
This section should identify all of the software functions and/or combination of functions that are not to be tested. The reasons why they will not be tested should also be included.
This section should identify all of the resources that will be required during the testing phase. This includes hardware, software, people, etc. The team members that are to be involved in testing and their roles and responsibilities during testing should be specified. People and groups that will be responsible for preparing, designing, managing, and executing the test activities should be included.
This section should provide the schedule of testing and specify all milestones. In addition, this is a good area to specify the documents that will be delivered (such as test plans, test cases, test results, etc.)
7.0 TESTING STRATEGY
This section should be used to describe the overall approach used during testing that will ensure that the features under test will be adequately examined. All tools, techniques, and activities should be specified here. The methodology for the various types of testing (unit, system integration, performance, stress, acceptance, etc.) should be outlined in this section. Methodology includes information such as the person that will create the tests, the series of events of testing, and how the testing activity will take place.
This section should provide detailed about the test environment. It should include specifications about the necessary hardware, software, any other tools, and the facilities that are required for testing.
9.0 PROCESS CONTROLS
This section should indicate the procedure that should be followed when an incident is encountered during the testing process as well as the process to implement software modifications. Personnel required to approve changes should also be identified in this section. Also, bug-tracking processes should be specified.
10.0 RISKS AND DEPENDENCIES
This section should indicate the risks associated with the test plan. Contingency plans should be provided for all listed risks. This section should also include any assumptions that were made when creating the test plan. This section should also identify any constraints on testing (i.e. resource availability, deadlines, etc).