140 likes | 168 Views
SOFTEC 2011 Using Test Policy and Test Strategy to get it Right. Anne Mette Hass. Do you sometimes feel like this when testing?. Maybe you need a test policy!. Do you always know where to go when testing ?. Maybe you need a test strategy!. Overview of test management documentation.
E N D
SOFTEC 2011 Using Test Policy and Test Strategy to get it Right Anne Mette Hass
Overview of test management documentation Project program Project Project Test policy Test strategy Project test plan Detailed test plan Organisation Project
Testing starts at the top Test policy is • the responsibility of top management • the organisation’s test philosophy • a brief, general document • may be part of a general quality policy … if management can’t formulate the policy – we’ll have to help them!
Trust is good Control is better Test is best Test policy could include • Objectives of testing • Test process • Test organization structure • Test education • Tester ethics • Standards • Other relevant policies • Measuring the value of testing • Test asset archiving and reuse • Test process improvement
Objectives of testing, Examples • “Ensuring that the software solves a business problem.” • “Activity designed to uncover information regarding the quality of the product.” • “Minimising product risks.” • “Toolbox of techniques for finding as many defects as early as possible”
The iterative dynamic test process from ISO 29119 Test Planning Test Design and Implementation Test Monitoring and Control TestEnvironment Set-up TestExecution Incident Reporting Change management Test Completion
Measuring the value • “Overall test efficiency should be greater than 98% measured after the first three months in production.” • “Customers should not report more than 3 type 1 failures in the first year of system use.” • “System downtime should be under 15 minutes for the first 6 months of operation.”
Test strategy follows on from test policy Test strategy should • be based on the test policy • be based on the risk profile for the product and the project • describe generic test requirements A test strategy may cover for example an entire organization, a programme of projects, or a project, and cover all test sub-processes in the scope
Test strategy structure from ISO 29119 General : Generic risk management Test selection and prioritization Test documentation and reporting Test automation and tools Configuration management of test work products Incident management Test sub-processes • Detailed strategy for • ’test sub-process 1’ • Entry and exit criteria • Test completion criteria • Test documentation • Degree of independence • Test design techniques • Test environment • Metrics to be collected • Retesting and regression testing • Detailed strategy for • ’test sub-process n’ • Entry and exit criteria • Test completion criteria • Test documentation • Degree of independence • Test design techniques • Test environment • Metrics to be collected • Retesting and regression testing • Test sub-processes may be: • Acceptance test • Integration test • Component test • Performance test • Load test • etc.
Influence from Strategy on the testing Entry criteria Test Planning Test Design and Implementation Exit criteria Test Monitoring and Control TestEnvironment Set-up TestExecution Test Completion