Test plan

A test plan is a document detailing a systematic approach to testing a system such as a machine or software. The plan typically contains a detailed understanding of what the eventual workflow will be.

A test plan documents the strategy that will be used to verify and ensure that a product or system meets its design specifications and other requirements. A test plan is usually prepared by or with significant input from Test Engineers.

Depending on the product and the responsibility of the organization to which the test plan applies, a test plan may include one or more of the following:

•     Design Verification or Compliance test - to be performed during the development or approval stages of the product, typically on a small sample of units.
•     Manufacturing or Production test - to be performed during preparation or assembly of the product in an ongoing manner for purposes of performance verification and quality control.
•     Acceptance or Commissioning test - to be performed at the time of delivery or installation of the product.
•     Service and Repair test - to be performed as required over the service life of the product.
•     Regression test - to be performed on an existing operational product, to verify that existing functionality didn't get broken when other aspects of the environment are changed (e.g., upgrading the platform on which an existing application runs).

A complex system may have a high level test plan to address the overall requirements and supporting test plans to address the design details of subsystems and components.

Test plan document formats can be as varied as the products and organizations to which they apply. There are three major elements that should be described in the test plan: Test Coverage, Test Methods, and Test Responsibilities. These are also used in a formal test strategy.


A test plan can be defined as a document describing the scope, approach, resources, and schedule of intended testing activities. It identifies test items, the features to be tested, the testing tasks, who will do each task, and any risks requiring contingency planning.


In software testing, a test plan gives detailed testing information regarding an upcoming testing effort, including

•     Scope of testing
•     Schedule
•     Test Deliverables
•     Release Criteria
•     Risks and Contingencies

It is also be described as a detail of how the testing will proceed, who will do the testing, what will be tested, in how much time the test will take place, and to what quality level the test will be performed.

One can have the following types of test plans:
 

• Master Test Plan: A single high-level test plan for a project/product that unifies all other test plans.
• Testing Level Specific Test Plans:Plans for each level of testing.
•         Unit Test Plan
•         Integration Test Plan
•         System Test Plan
•         Acceptance Test Plan
• Testing Type Specific Test Plans: Plans for major types of testing like Performance Test Plan and Security Test Plan.