Home TMap Digital transformation & The Technology Leaders

Determining the overall test planning

Aim

Creating the most reliable possible overall planning for all in-scope test levels, so that the client can take it into account or make adjustments. The principle of the planning is to find the most important defects first within the framework of the strategy and estimated effort.

Method of operation

Based on the planning of the system development process, the test strategy and estimated effort, an overall planning for the total test process is created. Factors observed while understanding the assignment, such a whether a time, money or quality-driven project is involved, have an impact on the planning. The start and end date and deliverables are specified for each test level. In the Planning phase of the various test levels, the detailed planning is elaborated. The overall planning must at least contain: 

  • Activities to be executed (at the phase level per test level)
  • Relationships with and dependencies on other activities (in or out of the
  • test process and between the various test levels) Time to be invested in each test level
  • Required and available resources (people and infrastructure)
  • Required and available lead time
  • Deliverables.

If requested by the client, the financial consequences of the choices made must be visualised in a financial planning. Think of costs for (internal and external) personnel, training, workplaces, test environments and test tools. 

The aim must be to ensure that the test execution activities for the various test levels match up or have a controlled overlap (overlap testing). When planning choices involving risks must be made for the sake of milestones, the test manager must report and explain this. 

A quality-related aspect of planning is when a test level is completed. The test manager therefore has an important role in aligning the entry and exit criteria of the successive test levels. 

In more detail

Example of exit/acceptance criteria 

In this example from practice, exit and acceptance criteria have high overlap.

 The test approach and acceptance criteria are tuned with the stakeholders (see section x.y). Two levels of acceptance can be distinguished: 

  1. Acceptance of system XYZ by all stakeholders. This involves releasing the products for production.
  2. Individual acceptance by the client(s) of each test level of the test level executed.

For level 1 acceptance, the test must be executed according to the agreed test strategy and the following guidelines are respected for any defects found: The products of XYZ can be taken into production (are accepted) if: 

  • There are no category A defects.
  • A patch or workaround is available for category B defects. The developer must also submit a planning reporting how and when the problem will be solved structurally. 
  • A document is available for category C defects, explaining how these non-critical defects are dealt with.

For level 2 acceptance, the test team (responsible for the relevant test level) will be discharged if the aims as defined globally in section y.z and further specified in detailed test plans, if any, are achieved. This is also a Go/No Go decision to start executing the following test level. 

Feedback

The test manager provides feedback on the combination of the selected test strategy, estimated effort and planning to the client for approval or adjustment. The client can opt for better risk coverage in exchange for more test time and funds, or vice versa. The previous steps for Strategy, Estimating and Planning are repeated, if necessary. To facilitate communication, the test manager refers back to the original test goals. 

Furthermore, he describes the use of tolerances in test execution with the client. These are boundaries within which the test manager does not have to ask the client for permission. Often a tolerance of 5% is used for the estimate, for instance. 

Products

The overall planning for the total test process, laid down in the master test plan Entry and exit criteria per test level  
Strategy, estimated effort and planning with feedback from the client  
Optional: Tolerances for strategy, estimated effort and planning. 

Techniques

Not applicable.

Tools

Planning and progress monitoring tools  
Workflow tool.

 

Continue to Determining the test level planning