Type to search

Testing Templates

Write Test Plan effectively, How?


In my previous post we looked what is test plan and why is it needed. Now we will look into how to write test plan effectively. And also each and every component of the test plan in detail.

Planning is important and essential part of our life. We plan each and every activity in life very carefully, so as we need to for testing activities.

Analyze the product

Could you be able to test without understanding product, answer No. To write test plan first of all we need to understand the requirements. So analyze requirements very carefully. Go through Product requirement document very carefully.

AnalyseTo know more, you should research clients and the end users know their needs and expectations from the application.

  • Who will use the application?
  • An application used for?
  • How will it work?
  • What is software/ hardware the product uses?

Write Test Plan

1) Test Plan Identifier

As the name suggests, ‘Test Plan Identifier’ is a unique identifier. It identifies the project, companies might follow a convention for a test plan identifier. Also contains information about the test plan type with version numbers. To know the different test plan types click here.

For Example Test Plan Identifier: ‘Test plan for <Project> _1. 0’.

2) Introduction

A summary of the test plan, including the purpose of the testing project and scope.

3) Test Items / Scope

This section includes all testing components, systems and sub-systems.

For example, For an e-commerce website, website, Database, Payment service (Third Party) etc.,

4) Features to be tested

In this section, in detail list all the features and functionalities to be tested. Most of all, the reference from BRD / RSD / FRS should be linked to each feature and functionality.

5) Features not to be tested

Should include all features / functionalities / components not to be tested. Furthermore, the reasons why these features not to be tested needed to be mentioned .

6) Test Approach

In this section, define test approach for testing. It contains common testing types, techniques and priorities. In addition, define testing types in detailed. Also contains information of the sources of test data, inputs and outputs.

7) Entry / Exit criteria

Define Entry criteria and Exit criteria. Entry criteria would be basically deployed to code to test environment. Exit criteria will be execution of all test cases.

Furthermore, acceptance criteria for number of defects can be open. For instance, No High and medium defects.

8) Test Schedule

Define the schedule for each phase of testing. Should consider buffer time for retest of defects and compensate environment down time etc.,. This schedule shall be in agreement with the development schedule to make a realistic test plan.

9) Testing Tasks

Define testing tasks in this section. Testing tasks may include creating test scenarios, creating test cases, creating test scripts, executing test cases, reporting bugs, creating an issue log.

Also include completion time for tasks where ever applicable. In addition define any dependencies.

10) Test deliverable’s

This includes all documents which need to be delivered at the end of testing.

For example, Test cases, Test Data, closure report etc.,

11) Item pass/fail criteria

In other words, this describes criteria for evaluating test cases, either pass/fail. Also defines criteria for overall pass percentage.

12) Suspension / Redemption criteria

This defines the criteria for suspension of testing activities and subsequently resumption criteria.

For instance, When the environment is down, including Integrity of components not stable, Major integration defects raised.

13) Environmental needs

Describes all environmental needs, including hardware, software and any other. Also, what is currently available and what need to be procured should be included.

14) Tools needed

Describes all tools needed for testing. For instance Tools and their licensing needs of automation. This section is optional as per IEEE 829 standards

15) Resources and Responsibilities

This section includes details about resources and their responsibilities. A resource could be human, equipment or materials.

The resource planning is an important factor of the test planning because helps Test Manager to correctly schedule & estimation for the project.

Also, mention the role and responsibility of each resource. For example,

1.     Test ManagerManage the whole project

Define project directions

2.     Test LeadIdentifying and describing appropriate test techniques/tools/automation architecture

Prepare Test Plan, Strategy and Approach

3.     TesterScript and Execute the tests, Log results, Report the defects.

16) Staffing and training needs

What type of resources are needed? In Addition, does anyone need additional or special training?

17) Risks and contingencies

Uncertain event which may cause potential loss is at Risk. Therefore, in this section you should describe all analyses risks and contingency plans for each risk.

Team member lacks the required skills on applicationPlan, training courses to skill up your members
The project schedule is too tight; it’s hard to complete this project on timeSet Test Priority for each of the test activities.

18) Documents / References

Here you will describe references to all documents and MOM which supports all points mentioned in this document.

19) Approvals

Finally, all approvals required for the document.


BRD: Business Requirement Document

FRS: Functionality Requirement specification

MOM: Minutes of Meeting

Leave a Comment

Your email address will not be published. Required fields are marked *