During test analysis and design the test approach is translated into tangible test conditions and test cases using test design techniques.
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.
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?
Specific Practice 1.2 – Identify and prioritise test cases
Test cases are identified and prioritised using test design techniques.
Typical work products –