Test Plan Details

Test Planning

1) Plan : Plan is a strategic document which describes how to perform a task in an effective, efficient and optimized way.

2) Optimization : Its a process of utilizing the input available resources to their level best and getting the maximum possible output.

Test plan Document

 Test plan is a strategic document which describes how to perform testing on the application in an effectively.

Test lead will design the Test Plan Document, Its contents are described below

1.0   Introduction

  1.1 Objective
      

Purpose of the document is specified over here.
     
  1.2 References Documents      

The list of all the documents that are reffered to prepare this document will be listed out here in this section. (SRS and Project Plan)

   
2.0   Coverage of Testing

  2.1 Features to be tested
      

The list of all the features that are to be tested based on the Implicit and explicit requirements from the customer will be mentioned in this section

  2.2 Features not to be tested     

 The list of all the features that can be skipped from testing phase are mentioned here, Generally Out of scope features such as incomplete modules are listed here. If severity is low and time constraints are high then all the low risk features such as GUI or database style sheets are skipped. Also the features that are to be incorporated in future are kept out of testing temporarily.
                       
3.0   Test Strategy

  3.1 Levels of testing      

Its a project level term which describes testing proceedures in an organization. All the levels such as Unit, module, Integration, system and UAT (User Acceptance test) are mentioned here which is to be performed.

  3.2 Types of testing
      

All the various types of testing such as compatibility,regression and etc are mentioned here with module divisions
     
  3.3 Test design techniques     

 The List of All the techniques that are followed and maintained in that company will be listed out here in this section. Some of the most used techniques are Boundary Value Analysis(BVA) and Equalence Class Participation(ECP).

 Boundary Value Analysis: 

 Equalance class participation:

  3.4 Configuration Management 

         All the documents that are generated during the testing process needs to be updated simultaneously to keep the testers and developers aware of the proceedings. Also the naming conventions and declaring new version numbers for the software builds based on the amount of chnange is done by the SCM ( Software Configuration Management team ) and the details will be listed here.
 
  3.5 Test Metrics

           The list of all the tasks that need to be measured and maintained will be present here.  Different metrics for tracing back the exact requirement and test case depends on the availability of metrics at the right time.

  3.6 Terminology

            Testing specific jargons for the project that will be used internally in the company wil be mentioned here in this section.

  3.7 Automation Plan

           The list of all the features , or modules that are planned for automation testing will be mentioned here. The application only undergoes automation testing after being declared STABLE by the manual testing team.

  3.8 List of Automated tools

          The list of Automated tools, like QTP , Loadrunner, Win runner, etc which will be used in this project wil be mentioned along with license details.

4.0   Base Criteria

   4.1 Acceptance Criteria

           The standards or metrics that need to be acheived by the testing team before declaring the product fit will be listed here. So before handovering to the customer, the time at which the testing needs to be stopped is mentioned here in this section.

  4.2 Suspension Criteria

          In high risk projects, or huge projects that consists several modules , It is necessary to minimize the repetitive process to be efficient. The situations when the testing needs to be suspended or temporarily halted will be listed here in this section.

       
5.0   Test deliverables

         The list of all the documents that are to be prepared during the testing process will be mentioned here in this section. All the copies of  verification documents after each level are submitted to the customer alongwith the user manual and product at the end of the project.

6.0   Test environment

          Environmental components and combinations that will be simulated for testing the product will be made sure that it is very close to the actua environment when the end user works on the product. All the details will be mentioned here in this section that is to be used for testing the application.

          
7.0   Resource planning

          Roles to be performed or in other words Who has to do What , will be mentioned clearly here.

8.0   Scheduling

          The starting dates and ending dates for each and every task and module will be listed here in this section.

9.0   Staffing and Training

          How much staff is to be recruited and what kind of training is to be provided to accomplish this project successfully will be described here in a detailed fashion.

10.0  Risks and Contingencies

           The list of all the potential risks and the corresponding solution plans will be listed here

           Risks : Example, Resources may leave the organization, license and update deadlines, customer may change the requirements in terms of testing or maintenance in middle of the project. etc

           Contingencies :  Maintaining bench strength, Rechecking initial stages of  the whole process, Importance and priority settings for features to be tested and features to be skipped under time constraints to be listed and shared clearly.

11.0  Assumptions

           Some features or testing methods have to be done mandatorily even though, the customer does not mention it in his requirements document. These assumptions are listed out here in this section.

12.0  Approval Information

           As this document is published and circulated, the relevant and required authorities will approve the plan and will update this section with necessary details like date and department etc.