Overview
In this post, let’s learn about Software Test Plan with a Software Test Plan Template.
A software test plan is a document that outlines the purpose of testing, scope, features to be tested, testing approach, test effort, schedule, risks, test sign-off criteria, etc. It is an important document that needs to be prepared during the planning phase of software testing.
Test Plan Template
Purpose
The purpose of this section is to give a brief description of the project in terms of the domain, technology used and the target audience, etc
Scope of Testing
The purpose of this section is to give a brief description of the various features that will be tested and the features that will not be tested.
- Include the critical features in the features to be tested
Testing Types
Following are the types of testing applicable/not applicable for the project:
In Scope | Out of Scope |
Features
Following are the features to be tested/not applicable for the project:
In Scope | Out of Scope |
Test Approach
The purpose of this section is to describe the approach that will be followed to perform the testing activities
- Include the process followed to author the test cases
- Include the process that will be followed to prioritize the test cases
Types of Tests to be conducted
The purpose of this section is to give a brief description of the various types of tests that will be performed on the application.
Requirements Traceability Matrix
The purpose of this section is to validate the test case preparation for all requirements as per the requirement document.
Test Case Preparation Approach
The purpose of this section is to describe the process followed for authoring the test cases
Test Execution Process
The purpose of this section is to describe the process followed for executing the test cases
Pass / Fail Criteria
The purpose of this section is to describe the pass/fail criteria.
Suspension and Resumption Criteria
The purpose of this section is to describe the process followed for suspend/resume testing.
Defect Management
The purpose of this section is to describe the process followed to log/track defects.
Following is the SLA for defect management:
S. No. | Severity | Time (Hrs.) |
1 | CRITICAL | |
2 | HIGH | |
3 | MEDIUM |
Test Effort and Schedule
Test Effort
The purpose of this section is to give a brief estimation of effort required and the number of resources required and an estimated duration for completing the testing activity.
Test Schedule
The purpose of this section is to enlist the start date and end date for each phase and the deliverables for the respective phases.
S. No. | Phase | Tasks | Start Date | End Date | Deliverables |
Test Environment
The purpose of this section is to give a brief description of the hardware/software requirements needed for performing the testing activities.
Hardware Environment
Software Environment
Test Tools
Tool Name | Purpose |
Staffing and Training Needs
The purpose of this section is to describe the training required for Training on the application/system and any test tools to be used.
Roles and Responsibilities (RACI)
The purpose of this section is to give a brief description of the roles and responsibilities.
Risks, Issues, and Dependencies
The purpose of this section is to list out logical assumptions, identify the prioritized risk and mitigation, and contingency plans, and identify dependencies (if any).
Risks
Outline Major Risks in the project.
Skill Gap Analysis
The purpose of this section is to continuously track the competency levels of the team’s present knowledge, identify gaps, bridge the gaps and enrich knowledge and skills to become masters in the skills required for the project.
Escalation Approach
For any escalations, the following are the points of contact during the test process for all test activities.
Role | Mobile | |
Acceptance and Sign-off Criteria
The purpose of this section is to identify the criteria accepted by the business and ensure quality is met.
Automation Testing
The purpose of this section is to give a brief description of the effort, schedule, and deliverables for automation testing.
S. No. | Phase | Tasks | Start Date | End Date | Deliverables |
Performance Testing
The purpose of this section is to give a brief description of the effort, schedule, and deliverables for performance testing.
S. No. | Phase | Tasks | Start Date | End Date | Deliverables |
Test Status Reporting
The purpose of this section is to enlist modes to be used to update the status to the client.
Test Metrics
Include information about metrics that will be used to showcase
—
Software Testing Tutorials:
https://www.testingdocs.com/software-testing-tutorials/