Download this free Test Plan template and use it for your new project. Scroll down to the bottom of the page for the download link.

1                    Introduction

1.1            Overview of the System

<Describe the overview of the application>

1.2       Purpose

<The purpose of this Test Plan is to clearly describe the various testing techniques and testing approaches followed for testing the system>

1.3       Acronyms and Abbreviations

<This subsection provide the definitions of all terms, acronyms and abbreviations required to properly interpret the Test Plan document>

2          Test Level

<Mention the applicable levels of testing – Unit, integration, system, acceptance and final acceptance. Describe a short description on how they are to be administered and if few are not applicable state why they are not available>

2.1       Test Level – Entry and Exit

Entry Level	Test Level	Exit Level
1. Functional Spec reviewed and available.   2. System Test Cases reviewed and ready.	System Testing	System test cases 100% executed.   No severity ‘Fatal’ or ‘High’ problem outstanding.   Test results documented in TPR.

Table 1 : Test Level – Entry and Exit

2.2       Test Levels and Test Items

Test Level	Test Items (Test Procedure, Test Cases, Scripts Reference)	Tools used (if any)	Coverage
System Testing	System Test cases	Manual	As per the Requirement Specification

Table 2 : Test Levels and Test Items

2.3            Exclusions

<No exclusions. The entire functionality as defined in the Requirement Specifications document shall be tested>

2.4       Test Criteria

2.4.1         Item Pass / Fail Criteria

<When the Expected Result matches with the Actual Result the corresponding Test Case is marked as ‘Pass’. Otherwise, the Test Case is marked as ‘Fail’. Test Problem Report (TPR) for failed test cases will be raised with a brief description of steps that actually lead to the issue. The Test Case ID is marked in the TPR against the Issue Description for better understanding. All issues in TPR shall be tracked to closure.>

2.4.2         Suspension and Resumption Criteria

<When 40% of executed test cases fail then testing would be suspended & the application would be returned to the development team for rework. Also testing would be suspended when the basic functionality is not met.

Testing would be resumed when the raised issues are fixed by the development team.>

2.4.3         Regression / Verification Criteria

< If the failed test cases percentage in more than 40% then regression testing would be performed else undergoes a verification cycle.>

2.5       Constraints and Deficiencies

< Inadequate time for Testing, Testing environment not available in time, Tester not familiar with the system, Delay in Receiving baseline documents, Delay in receiving the fixes from Development Team, Poor System Performance/response>

3          Test Reporting and Defect Tracking

<All defect raised during testing would be logged in an excel sheet>

4          Change Management

<Changes happen in the form of a requirement change or design change. Test plan and other test artifacts are analyzed for the impact due to change. Changes are then appropriately carried out and go through the same workflow as preparation, review, verification and baseline. Traceability matrix is revisited to accommodate the changes>

5          Test Planning

5.1       Roles and Responsibilities

Role	Responsibility	Person
Test Lead	Preparation of Test plan, Review of Test Cases, Testing, Test Monitoring and Test Consolidation and Analysis
Tester	Preparation of Test Cases, Testing Defect Reporting

Table 3 : Roles and Responsibilities

5.2       Test Schedule

Task	Start Date	End Date	Resource	Deliverable
Test case Preparation	<dd Month yyyy>	<dd Month yyyy>	<Name>	Test cases
Testing	<dd Month yyyy>	<dd Month yyyy>	<Name>	Test Problem report Test Summary Report

Table 4 : Test Schedule

<The above could be linked to the overall Project Schedule>

5.3       Environment Needs

5.3.1         Hardware

S. No	Testing Task	Hardware Details	Needed on or before

Table 5 : Hardware Details

5.3.2         Software

S. No	Testing Task	Software Details	Needed on or before

Table 6 : Software Details

5.4       Training Needs

< Give the training details to the Testing team. Could be specific to domain, technology and test tools >

S. No	Training Description	Needed on or before

Table 7 : Training Needs

5.5       Risk and Contingencies

S. No	Risk	Mitigation	Contingency

Table 8 : Risk and Contingencies

6          Customer Validation Plan

<Mention the steps taken for validating at the customer end. This would be UAT, FAT or intermediate testing or parallel testing. This section needs to indicate the various types of validations planned, validating components and the schedule>

6.1       Roles and Responsibilities

<State the various roles and their responsibilities here in this section. This could be in overall sync with the PMP roles and responsibilities >

Role (Customer end and COMPANYNAME)	Responsibility	Person

Table 9 : Customer Roles and Responsibilities

6.2       Validation Schedule

<Give the complete validation schedule and this has to be part of the overall project schedule>

Validation Item <Build or Prototype or Component inclusive of iteration>	Start Date	End Date	Entry Criteria	Exit Criteria

Table 10 : Validation Schedule

* The above could be linked to the overall Project schedule

6.3       Validation Environment Needs

< Give the testing hardware/software environmental details here. This is inclusive of all test levels, techniques and in terms of hardware and software. Also mention the location where the validation would be done >

6.3.1         Hardware

S. No	Hardware Details	Needed on or before

Table 11 : Validation Hardware Details

6.3.2         Software

S. No	Software Details	Needed on or before

Table 12 : Validation Software Details

6.4       Validation Items

<Mention what are the items that have to be used for validation. These would be scenarios or scenario test cases or some cases written and given by customer. Mention what would be the validation items customer would use>

6.5       Reporting and Tracking to Closure

<Mention how customer validation results would be reported – either in TPR or customer given format and also mention how they will be tracked to closure>

Click here to download Test Plan Template.