Ten Small But Important Things To Observe In Test Plan Document: Definition, Components, Template

Test Plan :
  • Test plan consists of future testing activities to be done like the number of resources required in a project, Types of testing to be done, Test estimation, etc.
  • With the help of a test plan, we can determine the efforts needed to verify and validate the quality of the application under test.
  • A Test plan is monitored and controlled by the test managers.

Test Plan Components :   

The Test plan consists of the following components:

  •  Description: Here we describe the application in a few lines like what is the application all about.
  • Objective: Here we specify the aim of the project.
  • Test Scope: Here we list out, the feature to be tested and the feature not to be tested.
    • Example: In the Gmail application, I will test the following pages.
      • Compose.
      • Inbox.
      • Sent Items.
      • Drafts.
      • Spam etc.
    • List of items which, I will not test.
      • Youtube.
      • google docs.
      • google maps.
      • google-plus etc.
  • Approach: Here we specify what will be the approach as a team while we are working on the project. Ensure there is maximum communication between team members.
  • Assumption | Risk | Mitigation Plan: In a project when an assumption fails it leads to risks, so whenever there is a risk we should have a plan to mitigate that risk.
    • Example: In a project, the assumption was there will be 3 resources throughout the project. But if anyone employee quits the job then that creates risk is the project, To resolve this risk we have to recruit backup resource and we also have to ensure that every employee will have to serve notice period, this will be the mitigation plan to solve the risk.
  •  Types of Testing: Depending on the project we decide the types of testing to be performed. 
  • Role and Responsibility: Here we very clearly specify the job and responsibility of the Manager, Lead, Testers.
  • Hardware and Software Requirement: Here we specify what kind of server is required.

    • Example :
      • HP xenon processor.
      • 64 GB RAM.
      • 2TB Hard Disk.
      • Windows Server 2012. 
    • Here we also specify what kind of client computers are required.
      • Example :
        • i5 processor.
        • 4GB RAM.
        • Window's 10 etc.
  • Defect Tracking: In this section, we specify which defect tracking tool we are going to use.
    • Example: Bugzilla, Mantis, Jira, etc.
  • Entry and Exit criteria: It helps us to decide when to start a particular type of testing and when to stop a particular type of testing.
    • Example: Entry Criteria for functional testing.
      • The Smoke test should pass.
      • All the test cases should be ready.
      • White box testing should have been done.
      • Resources should be available.
    • Exit Criteria for Functional Testing:
      • Most of the test cases should have been executed.
      • There should not be any critical defects.
    • Entry Criteria for Integration testing :
      • Exit Criteria of functional testing should be met.
      • The Smoke test should pass.
      • All the test cases should be ready.
      • White Box Testing should have been done.
      • Test cases should be available.
  • Template: Here we specify, the format of test cases, STCM(Software Test Coverage Matrix), Traceability Matrix, etc. Which we are going to use in the project.
  • Schedule: Here we define the test estimation to finish each and every testing activity.
    • Example :


  • Deliverable: In the deliverable, we are going to specify along with the software what all will be given to the customer.
    • Example :
      • Installation CD.
      • User Manual.
      • Test Cases.
      • Defect Report(Graphical Report).
      • Test Plan.
      • Release Note.

                         Test Plan Template


1. Description.......................

2. Objective..........................

3. Test Scope………………

        3.1 In scope

        3.2 Out Of Scope

4. Roles and Responsibilities…………

5. Test Methodology……………….....

6. Types of Testing……………………

7. Defect Tracking……………………

8. Approach……………………………

9. Entry and Exit criteria………………

10. Deliverables………………………..

11. Hardware and Software Requirement

        11.1 Testing Tools

         11.2 Test Environment


  1. Description

Brief introduction about the project.

 2. Objective

    Detailed description about what is the aim of the project.    

 3. Test Scope

 3.1 In Scope

Scope defines the features of the software which will be tested   

3.2 Out of Scope

Out Of Scope defines the features of the software not to be tested. 

4. Roles and Responsibilities

Detailed description of the Roles and responsibilities of different team members like:

·    QA Analyst

·    Test Manager

·    Configuration Manager

·    Developers

·    Installation Team

5. Test Methodology

Specify the reason for using a particular test methodology for the project. The methodology selected for the project could be :

·    Waterfall Model

·    Agile

·    Extreme Programming

·    Spiral Model

·    Prototype Model.

·    V-Model

The methodology selected depends on multiple factors. You can read about Software Development Models here

6. Types of Testing

Depending on the project we decide the types of testing to be performed like.

·    Smoke Testing.

·    Functional Testing.

·    System Testing.

·    Integration testing, etc.   

7. Defect Tracking

The goal of defect tracking is to

· To define the type of resolution for defects

· To prioritize defects and determine a schedule for all "To Be Fixed Defects".

· Which defect tracking tool we are going to use.  

8. Approach

We have to specify what approach to follow as a team while we are working on a project.

9. Entry and Exit criteria

Here we have to define when to start a particular type of testing and when to stop a particular type of testing 

Example: Entry Criteria for functional testing.

      • The Smoke test should pass.
      • All the test cases should be ready.
      • White box testing should have been done.
      • Resources should be available.

Exit Criteria for Functional Testing:

      • Most of the test cases should have been executed.
      • There should not be any critical defects.

10. Deliverables

In the deliverable, we are going to specify along with the software what all will be given to the customer.

Here are the sample deliverables

      • Installation CD.
      • User Manual.
      • Test Cases.
      • Defect Report(Graphical Report).
      • Test Plan.
      • Release Note

11.        Hardware and Software Requirement

11.1   Testing Tools

Make a list of Tools like

·    Requirements Tracking Tool

·    Bug Tracking Tool

·    Automation Tools

11.2   Test Environment

It mentions the hardware requirements used to test the Application. 

Following softwares are required : 

·    Windows 8 and above

·    Office 2013 and above

·    MS Exchange, etc.


                    Download Test Plan Template 

Comments

Popular posts from this blog

What is smoke testing?How to perform smoke testing?Difference between smoke and sanity?

Test Case Design Technique in Software Testing With Examples

Monkey Testing & Usability Testing? Examples, Advantages