Test Plan Document:

Test Plan Document:

This document is prepared by the Test lead once they get the approved test strategy document from the test manager.

The test plan document is dependent on Build release.  

Contents of Test Plan Document:  

      Title: It describes the name of the project with type of document

Example: Banking System Test Plan v1.0 à describes the type of the document with version number where v1.0 represents initial version of first module.

·         History Of Document: It describes about the details of author of test plan document, when it was prepared, who conducted reviews, change of notifications and approval of test plan document.

·         Introduction :

Ø Project Overview: Brief description about the application under test.

Ø Objective of Test Plan: Brief description about the current test plan document.

Ø Referred Documents: About the documents referred to prepare the test plan document.

Example: BRS and FRS documents.

Ø Scope :

ü    In Scope:  It describes the possible testing activities under current test plan like functionality testing, usability testing, etc…

ü    Out of Scope: It describes the activities which are not possible under current test plan like unit testing, integration testing, performance testing, etc…

·         Features to be tested: It describes about the available modules and requirements in current build to validate

·         Features not to be tested: It describes about the modules and requirements which are not required to validate.

·         Entry & Exit Criteria:

a)      Entry criteria describe when to start testing or when to perform dynamic testing or when to perform test case’s execution.

The factors which were considered in entry criteria,

      All the test cases should be prepared and reviewed.

      Build should be deployed (installed) at test environment.

      Build should pass sanity test. i.e., build must be stable.

      Test environment setup should be completed.

b)      Exit criteria describe when to stop testing activities.

The factors which were considered in exit criteria,

      All the test cases should be executed atleast once.

      Majority of the test cases should be passed.

      Identified defects should be closed or postponed.

      Defect ratio must be less than acceptance level.

      Budget and time constraints should be keep in mind.

      When UAT is completed then test engineers can stop testing.

·         Suspension & Resumption Criteria:

a)      Suspension Criteria: It describes when the test engineer can suspend the test cases    execution.

The factors which were considered in suspension criteria,

      When build is not stable, means when it is failed in Build Verification Test.

      When there is a change request from client.

      Delay in publishing input documents.

      Whenever test engineer identifies showstopper defect.

b)                  Resumption Criteria: It describes when to continue the test execution after suspension.

The factors which were considered in resumption criteria is,

      When the patch file is released for rejected build.

      When requirements are refined based on client request acception or rejection.

      When input documents are publishes.

      When showstopper defects are resolved.

·         Testing Approach: It describes the testing approaches they will be using to validate the application functionality.

Example: Usability testing, functionality testing, compatibility testing etc…

·         Roles & Responsibilities: It describes the test engineer names and allocated tasks to perform.

·         Schedule: It describes the timelines to perform each activity during testing.

·         Test Environment: It describes the required environment setup for test cases execution like hardware and software configurations in the system to run the test cases.

Example: Browser setup, OS settings, etc…

·         Test Deliverables: The document which needs to be delivered at end of every task in testing is known as test deliverables.

Here in entire testing process after every phase the documents regarding to that phase must be delivered to the appropriate officials.

Example: Test Cases Review Report, Test Cases Execution Report, etc…

·         Risks & Mitigations: It describes the possible risks and the solutions for those risks at the test environment and work environment.

Example: Lack of domain knowledge to test engineers , here the solution is conducting KT sessions .

Note: Once the test plan document is prepared, the test leas conduct review with senior test engineers to get it approved and then the approved test plan document is delivered to the test engineers of the team.

Interview Question: What is showstopper defect???