Project Name:
Prepared By: (Name of the key people from the testing team)
Revision History: (Description of any changes made, version number, who made the changes, and
date when the changes were made)
(Table of Contents)
1. Overview
1. General description of the project
2. In Scope
o
What will be tested (major testing tasks)
o
The plan for testing (how the testing will be conducted)
o
What resources are needed
2. Testing
1. Methodology to be followed during the testing
2. Description of the methodology
3. Platform Testing
o
Specify the platform your software will be tested for
4. Regression Testing
o
Identify if regression testing is needed
5. Other Testing Types
o
Security testing
o
Connectivity testing
o
Disaster recovery testing
o
Integration testing
o
Unit testing
o
User acceptance testing
o
Automation testing
o
Stress testing
3. Testing Strategy
1. What kind of approach is taken
2. Who is responsible for each test
4. Test Schedule
1. Dates of execution
2. Prioritization of functions to be tested
5. Facility and resources needed
1. Resources and skills
2. Test environment
o
Operating system
o
Version of the operating system
o
Hardware configurations
o
Software dependencies
o
Network configuration
3. Any special access needed
4. Data set for testing
6. Tools
1. Define what tools are needed for testing
7. Test Metrics
1. Define what metrics need to be recorded and the reasons to record them
8. Control Measures
1. Define any control measures for the testing environment
9. Roles and responsibilities
1. Roles and responsibilities of the people associated with each testing phase
10. Criteria Determination:
1. List of criteria to be used to determine the success of the testing
2. List of criteria to be used to determine when to abort the testing
3. Resumption criteria to determine when to resume testing once paused
11. Use Case Documents/resources:
1. Use case name and ID number
2. Description of the use case
3. Preconditions for the use case
4. Successful execution scenario of the use case
5. Alternate execution scenarios of the use case
6. Exit criteria for the use case
12. Administration
1. Approvals
2. Training
13. References