Test Plan Template

Project Name : (XYZ)

1. Introduction:
The Software Test Plan (STP) is designed to prescribe the scope, approach, resources, and schedule of all 
testing activities. The plan must identify the items to be tested, the features to be tested, the types of testing to be performed, the personnel responsible for testing, the resources and schedule required to complete testing, and the risks associated with the plan.

1.1 Objectives :
Describe, at a high level, the scope, approach, resources, and schedule of the testing activities. Provide a concise summary of the test plan objectives, the products to be delivered, major work activities, major work products, major milestones, required resources, and master high-level schedules, budget, and effort requirements. 

1.2 Testing Strategy :  Testing is the process of analyzing a software item to detect the differences between existing and required conditions and to evaluate the features of the software item. 

Specific test plan components include:

• Purpose for this level of test,
•  Items to be tested,
• Features to be tested,
• Features not to be tested,
• Management and technical approach,
• Pass / Fail criteria,
• Individual roles and responsibilities,
• Milestones, 
• Schedules, and
• Risk assumptions and constraints.  

1.3  Scope :
Specify the plans for producing both scheduled and unscheduled updates to the Software Test Plan (change management). 

1.4 Reference Material :
Provide a complete list of all documents and other sources referenced in the Software Test Plan.
• Project authorization,
• Project plan,
• Quality assurance plan,
• Configuration management plan,
• Organization policies and procedures, and
• Relevant standards

2. TEST ITEMS :
Specify the test items included in the plan. Supply references to the following item documentation:
• Requirements specification,
• Design specification,
• Users guide,
• Operations guide,
• Installation guide,
• Features (availability, response time),
• Defect removal procedures,
• Verification and validation plans.

3. FEATURES TO BE TESTED :
Identify all software features and combinations of software features to be tested. Identify the test design specifications associated with each feature and each combination of features.
4. FEATURES NOT TO BE TESTED :
Identify all features and specific combinations of features that will not be tested along with the reasons.

5. APPROACH : 
Describe the overall approaches to testing. Describe the specific methods and procedures for each type of testing. Define the detailed criteria for evaluating the test results.
6. PASS / FAIL CRITERIA : 

 Specify the criteria to be used to determine whether each item has passed or failed testing.

7. TESTING PROCESS : 
Identify the methods and criteria used in performing test activities. Define the specific methods and procedures for each type of test. Define the detailed criteria for evaluating test results.

8. ENVIRONMENTAL REQUIREMENTS :
Specify both the necessary and desired properties of the test environment including the physical characteristics, communications, mode of usage, and testing supplies. Also provide the levels of security required to perform test 
activities. 
Hardware
Software
Security
Tools
Risks and Assumptions

9. CHANGE MANAGEMENT PROCEDURES : 
Identify the software test plan change management process. Define the change initiation, change review, and change authorization process.
10. PLAN APPROVALS : 
Identify the plan approvers. List the name, signature and date of plan approval.