PA 2.2. SG 2 – Establish a test approach

A test approach, based on identified product risks, is established and agreed upon.

Introduction

A test approach will usually identify the high level activities which will be performed for a particular test project. An approach is not a generic document like a test strategy or a generic framework. An approach document will be project-specific.

For this Goal it is important to ensure that the purpose of the document is fulfilled. It is not a weakness if there is another document produced which fulfils the purpose of an approach document but has a different name.

Specific Practices

SP 2.1 Identify items and features to be tested

Features of the product have been identified that will be in and out of scope of planned testing activities. This includes functional and non-functional features.

SP 2.2 Define the test approach

Test levels required and other elements within this area are specified (for example, test design techniques to be applied, which features to be tested at which level).

SP 2.3 Define entry criteria

Comprehensive entry, exit and suspension / resumption criteria to be applied at all test levels are defined to demonstrate adequate quality and progress.

SP 2.4 Define exit criteria

SP 2.5 Define suspension and resumption criteria

Deployment notes

  • Are items and features to be tested (and not to be tested) identified and prioritised based on the product risks?
  • Is an approach to test defined to mitigate the high priority risks? For example, test design techniques, levels of testing, coverage, re-test, regression test and test tools support.
  • Are sufficient entry, exit and suspension / resumption criteria defined to manage the test life cycle?
  • Is the test approach and other elements aligned with the test policy, goals and strategy?
  • Is there clear evidence that all relevant stakeholders are consulted at all stages and have the opportunity to review and agree these elements?