Development of Test Plan

The Test Plan is a document that describes the entire volume of the testing work spent or planned on a specific project.

It is created before the testing of the project and must be approved by the customer and all stakeholders.

The Test Plan covers items such as:

  • description of the testing object;
  • definition of testing purposes and strategies;
  • definition of project priorities and the role of testing;
  • definition of the criteria for the beginning and end of testing;
  • the choice of test environment;
  • writing of test-cases

There are two main types of Test Plans:

  • Master Test Plan - contains static high-level information that never changes. It is used to get acquainted with the basic components of the project and its development process. As a rule, there is only one for the entire project;
  • Detailed Test Plan - contains more specific information concerning strategies, types of testing, the schedule of works. It changes constantly, reflecting the real state of the project.

The latest version of the Test Plan should always reflect the real state of the project. If the project is large, it is advisable to create a detailed test plan for each subsystem or component of the project and additional master test plan for covering the strategies and approaches for the complete project.

Below you can find an example of the Test Plan prepared by the QATestLab specialists.

QATestLab Testplan Project Name