Test Plan is a document detailing the scope, approach, resources and schedule of the intended test activities. It specifies the features to be tested, the testing tasks, test documents, roles and responsibilities, test environment, test design techniques, staffing and training needs, entry and exit criteria to be used and any risks requiring contingency planning.
Test Plan can be used for Unit, ST (System Testing), UAT (User Acceptance Testing) or any other phase of testing which is in scope and should cover and discuss all the test related activities for that phase. A Testing team member (Test Manager / Test Lead / Test Analyst ) is responsible for creating a Test Plan.
Most of the sections are self-explanatory. I’ll cover some of them below for better understanding.
The Scope section covers all the Functional and Non-Functional testing that is going to happen in the project and any Out of Scope testing.
Test Approach defines the overall approach and various test techniques like Risk Based Testing approach to carry out the testing activities, number of Test Cycles required.
Roles and Responsibilities section lists all the Project Team members, their roles, what tasks are expected from them and important contact numbers.
Test Environments are very important for the Testing. A schedule to use the environment needs to be discussed and agreed with the Test Environments owner as there could be a number of projects planning to utilise the particular environment for testing. The usage dates clashes need to be dealt very carefully considering the project priorities and other factors. The owner of the Test Environment can be a Testing team member or from the Infrastructure team.
Release Management is another area often neglected by the project teams. The process to get the release of the builds or versions of the software and deployment (including approvals) has to be agreed, especially in the vendor-client relationship.
The Entry & Exit criteria always have one or two exceptions which need to be approved by the stakeholders before moving ahead.
Test Plan
Test Plan can be used for Unit, ST (System Testing), UAT (User Acceptance Testing) or any other phase of testing which is in scope and should cover and discuss all the test related activities for that phase. A Testing team member (Test Manager / Test Lead / Test Analyst ) is responsible for creating a Test Plan.
Most of the sections are self-explanatory. I’ll cover some of them below for better understanding.
The Scope section covers all the Functional and Non-Functional testing that is going to happen in the project and any Out of Scope testing.
Test Approach defines the overall approach and various test techniques like Risk Based Testing approach to carry out the testing activities, number of Test Cycles required.
Roles and Responsibilities section lists all the Project Team members, their roles, what tasks are expected from them and important contact numbers.
Test Environments are very important for the Testing. A schedule to use the environment needs to be discussed and agreed with the Test Environments owner as there could be a number of projects planning to utilise the particular environment for testing. The usage dates clashes need to be dealt very carefully considering the project priorities and other factors. The owner of the Test Environment can be a Testing team member or from the Infrastructure team.
Release Management is another area often neglected by the project teams. The process to get the release of the builds or versions of the software and deployment (including approvals) has to be agreed, especially in the vendor-client relationship.
The Entry & Exit criteria always have one or two exceptions which need to be approved by the stakeholders before moving ahead.
Follow and Like us:
Test Plan
No comments:
Post a Comment