An organisation-wide or programme-wide test strategy is established and deployed, identifying and defining the test levels to be performed.
This Specific Goal seeks to ensure that the organisation has a document that identifies and defines the test levels to be performed,with the objectives, responsibilities and tasks needed, that a generic risk assessment is carried out, that and that it is all reviewed with stakeholders.
SP 2.1 Perform a generic product risk assessment
SP 2.2 Define test strategy
- The test strategy is drafted as a generic document that contains all defined elements of how testing will be undertaken in order to satisfy the test policy and test goals.
- It is the overall approach to test effort and provides the required framework.
- Some subjects that should be covered are:
- Generic risks of the products being developed
- Overall test model (for example V-model, incremental life cycle) as a way to mitigate the risks
- Test levels (for example, unit, integration, system or acceptance test)
- Objectives, responsibilities and main tasks at each test level. For example: for unit testing
- verifying that the unit operates as specified in the unit design
- a certain level of code coverage is achieved
- for integration testing
- verifying that the units operate together as specified in the global design
- verifying that the interfaces operate as specified in the interface specifications
- for system testing
- verifying that the system operates as specified in the requirements specification
- a certain level of system requirements coverage is achieved
- for acceptance testing
- verifying that the system satisfies acceptance criteria
- validating whether the system is ‘fit for use’
- a certain level of user requirements coverage is achieved
- Test case design techniques to be used at each test level
- Test types to be carried out at each test level
- Entry and exit criteria for each test level
- Standards that must be complied with Level of independence
- Environment in which the tests will be executed
- Approach to automation at each test level
- Approach to regression testing
SP 2.2 Distribute the test strategy to stakeholders
- Has a generic product risk assessment been undertaken?
- Has the organisation (at programme or organisational level) defined the required strategy / approach / framework to provide clear guidance on how the test function will undertake testing and debugging to satisfy the policy and goals?
- Are test levels, objectives, activities, roles, responsibilities, main tasks, entry / exit criteria defined in the test strategy (the overall approach of how to satisfy the ‘what’)?
- Does the test strategy / approach outline how to approach testing activities with other associated elements such as approach to risk and regression testing?
- Is the test strategy reviewed with stakeholders?
- Is the test strategy publicised to, and discussed with, stakeholders?