Process Area 2..4 – Test Design and Execution – SG 1 – Perform test analysis and design using test design techniques

During test analysis and design the test approach is translated into tangible test conditions and test cases using test design techniques.

Introduction

This Specific Goal looks to see that, during test analysis and design, the test approach is translated into tangible test conditions and test cases using test design techniques.

Specific Practices

SP 1.1 Identify and prioritise test conditions

This Specific Goal is looking to have demonstrated that projects follow a structured approach for identifying high-level test conditions (or test objectives) against the identified product items and features. It also looks to see if structured test design techniques (equivalence partitioning, boundary value analysis, state transition tables etc.) are utilised in ensuring that the best possible sub-set of test conditions are identified to test particular items and features.

SP 1.2 Identify and prioritise test cases

Once test conditions have been identified, are test cases specified to ensure that test conditions are executed properly and completely. This includes documenting all aspects including pre- and post-requisites and test environments.

SP 1.3 Identify necessary specific test data

It is also necessary to identify and document data requirements for all identified and planned test levels.

SP 1.4 Maintain horizontal traceability with requirements

Once the test cases are specified, is there a robust and complete traceability between the test ware and the product items or features to enable reporting on coverage?

Deployment notes

• Is an appropriate, structured approach (using applicable test design techniques) applied to identify the test conditions based on analysis of the test basis?
• Are these prioritised according to risk and documented in an appropriate format?
• Are the test conditions reviewed with stakeholders as and when the test basis changes?
• Are test cases derived from test conditions?
• Are required elements documented (pre-requisites, expected results etc.) and reviewed with stakeholders?
• Are test data requirements for test cases identified and documented?
• Is horizontal traceability between requirements and test conditions / cases defined, maintained and used to establish test coverage?

Example Sub-practices and work products

Specific Practice 1.2 – Identify and prioritise test cases

Test cases are identified and prioritised using test design techniques.

Typical work products –

• Test cases
• Test case specifications

Sub-practices

• Derive the test cases from the test conditions using test design techniques. A test case consists of a set of input values, execution preconditions, expected results and execution post conditions.
• Prioritise the test cases based on identified product risks
• Document the test cases in a test case specification, based on the test case specification standard
• Review the test case specifications with stakeholders
• Revise the test case specifications as appropriate