Professional Documents
Culture Documents
Test Plan Template
Test Plan Template
Revision History
Pages
Version Date of Release Description of change Author
Affected
Table of Contents
1.0 Introduction.
1.1 Purpose.
1.2 Product Overview.
1.3 Scope.
1.4 Document Reference.
1.5 Intended Audience.
8.0 Tools.
9.0 Deliverables.
10.0 Appendix.
1.0 Introduction
1.1 Purpose
The purpose of this document is to describe the Validation strategies adopted for testing the
<Product Name> application.
1.3 Scope
The scope of this document is to explain the Testing Strategies, Test Environment, and Resource
Usage for testing the <Product Name> application.
1. Unit Testing
2. Integration Testing
3. System Testing
4. Regression Testing
5. Performance Testing
6. Production Environment Testing (at R&D Center and at client site)
7. User Acceptance Testing
• Equivalence Partitioning
• Error Guessing
Entry Criteria
• Base lined design document
• Base lined code
• Base lined test plan document
• Unit test case document
Work Items
• Test execution
Exit Criteria
• Test execution report
• Unit testing review checklist
Test Conditions
• Behavior of Individual Modules.
• Integration between different modules
Entry Criteria
• Base lined design document
• Base lined Functional specification document
• Base lined code
• Base lined test plan document
• Unit test execution report
• Integration test case document
Work Items
• Test execution
Exit Criteria
• Test execution report
• Integration review checklist
Test Conditions
• Functionality of the application with respect to its behavior on the whole, with
compliance to its hardware and software.
Entry Criteria
Work Items
• Test execution
Exit Criteria
• Test execution report
• System review checklist
Test Conditions
• Functionality of the application on the whole. (Refer Unit / Integration / System
Checklists).
Entry Criteria
• Unit test review checklist
• Integration test review checklist
• Base lined test plan document
• Unit / Integration test case documents
Work Items
• Test execution
Exit Criteria
• Test execution report
• Regression review checklist
Test Conditions
• Performance of the application at stipulated parameters
Entry Criteria
• Base lined test plan document
• Performance test case / scenario document
• Performance parameter specification list
Work Items
• Test execution
Exit Criteria
• Test execution report
• Performance review checklist
Test Conditions
• The behavior of the completely built application at the production and the client
site. (Refer the checklists for Unit / Integration / System and User Acceptance
Testing).
Entry Criteria
• Base lined design document
• Base lined Test plan document
• Compiled EXE file of the application
• Unit / Integration / Regression / Performance Test execution reports
Work Items
• Test execution
Exit Criteria
• Test execution report
• Production Environment review checklist
Test Conditions
• The behavior of the application as per the client’s requirements.
Entry Criteria
• Base lined software requirement document
• Base lined design document
• Base lined test plan document
• Unit / Integration / Regression / Performance / Production environment test
execution reports
Work Items
• Test execution
Exit Criteria
• Test execution report
• UAT review checklist
5.0 <Product>
Give a brief description of the working of the product.
NOTE: This is optional. If you wish that this section should be there, keep it. Else, you
can ignore this section.
Test cases thus generated will be executed and deviation in functionality will be reported as errors
for correction.
Category Description
Severe Functionality not working.
Major Serious effect to the functionality.
Minor Minor deviation in the functionality.
Cosmetic Errors with respect to User Interface.
Suggestion Suggestion for improvement.
The errors identified would be reported to the Development Team through a Defect Tracking Tool.
Regular meetings between the Test team and the Development team would be organized to have
continuous updates on the status.
Level Description
Must Fix Fix the bug at the Immediately.
Should Fix Important, Fix at the earliest.
Fix when have time Fix the bug when time permits.
Low Priority Not exactly a bug.
Status Description
Open The error reported is open.
When the test engineer opens a bug, the developer resolves the bug and changes the status of
the error to “Resolved”. The test engineer re-tests the error and Closes. If the error is repeated
while in any phase of testing, the error would be re-opened.
In this section mention the fields in the bug report form and how one should log in the bugs.
Item Description
8.0 Tools
The following tools would be used by the team members during the course of the project.
Purpose Tool
Defect Tracking Tool
Configuration Management
Scheduling
9.0 Deliverables
The following documents would be maintained by the Test team.
The Test Schedule would be maintained in a Microsoft Project file with reference to the Test Plan.
The schedule will be affected whenever there is a change in the schedules of the Project Plan.
10.0 Appendix
Enclose here any appendices you need.