Test Plan Document

Hello Friends,

Welcome to All About Software Testing blog.

 

In last blog we took the important STLC process, In this Blog we are going to see about Test Plan Document. 

Test plan is the most important question in interview, whenever I have to prepare for the interview I have prepare the following points, so If any buddy would ask me about test plan, this time I explain this following points.

What is Test Plan?

Test plan is a document which design and develop for executing the testing process in systematic way. Test plan is similar like user manual or day to day activity instructions.

This document is developed by Test team lead. In test plan Test lead mentioned all the details for a team which are followed while doing testing. So this is not just one person affords test plan is the continues activity which is followed by each team member.

Test plan usually developed during the early phase of the project.

Test Lead mentioned the following details in test plan, This plan might be change as per the Team Lead, so this is just for your reference.

Test Objectives

The test Objectives provide a prioritized list of verification or validation objectives for the project. You use this list of objectives to measure testing progress, and verify that testing activity is consistent with project objectives.

Scope and Risks

While doing the risk analysis test lead’s experience is most important factor, He is assuming what kind of difficulties might be comes in future.

In scope analysis test lead mentioning about important functionality which will going to test (Scope and Out of scope functionality).

•        Features to be tested: Important features that needs to tested.

•       Features not to be tested: Identify the features and the reasons for not including as part of testing.

In out of scope, you have to mention what are the things which are not dealing with.
If you will not going to perform Performance testing you have to mentioned in the Test plan.
Or If any module required some data for testing and the data is not available this time the particular module is out of scope and need to mention in your test plan document.
  
Test Strategy
On the basis of different phases strategy will change.
Unit testing, Integration testing, system testing and last acceptance testing.

Estimation

Work estimation is calculated before the completing the test plan.

Some peoples are using formula to calculate the time as per the activities, but in next article I will share very easy and useful test estimation process. In this section work is divided into the working hours.

Holidays and employee’s leaves also consider while calculating the Estimation.

Schedule

Scheduling is more about how much time we are giving to take.

Test lead will decide what to test? when to test? and who to test?

Team lead will mention the Start date and End Date for the test Execution Cycle.

Resource Planning

Means what kind of resources we need to use in this testing cycle, for example Hardware, software, team members, network devices.

Resource planning also known as team formation, team member and his task will decide in the resource planning.

Plan Test Environment

In this section team lead will decide the test bed(Testing Environment ), Actually this information is collecting from the client. In which environment the developed module will going to run, so on this basis test environment is decided.

Test Execution

Entry criteria for the test execution is Test cases, so before starting the Test Execution testers should create the Test cases, and execute that test cases as per the condition mentioned in test case document.

In this phase Bug life cycle is introduce.  

I hope you like this article, in next article we will see the creation of Test Estimation Documents.

So please share this link with your friends and add a comment for improvement.

Thank you.