Transcript Slide 1

SOFTEC 2011
USING TEST POLICY AND TEST STRATEGY TO GET IT RIGHT
Anne Mette Hass
CONNECTING
BUSINESS & TECHNOLOGY
2
COPYRIGHT©
DO YOU SOMETIMES FEEL LIKE THIS WHEN TESTING?
3
COPYRIGHT©
MAYBE YOU NEED A TEST POLICY!
4
COPYRIGHT©
DO YOU ALWAYS KNOW WHERE TO GO WHEN TESTING?
5
COPYRIGHT©
MAYBE YOU NEED A TEST STRATEGY!
Test policy
Organisation
Test strategy
Project program
Project
User
requirements
Project
Acceptance
testing
User
requirements
Integration
testinginthelarge
Product design
System
requirements
System
requirements
Systemtesting
Architectural
design
Acceptance
testing
Integration
testinginthesmall
Detailed
design
Integration
testinginthelarge
Product design
Systemtesting
Architectural
design
Component
testing
Coding
Project test plan
Project
Acceptance
testing
Integration
testinginthelarge
Product design
6
Component
testing
Coding
User
requirements
Detailed test plan
Integration
testinginthesmall
Detailed
design
System
requirements
Systemtesting
Architectural
design
Integration
testinginthesmall
Detailed
design
Component
testing
Coding
COPYRIGHT©
OVERVIEW OF TEST MANAGEMENT DOCUMENTATION
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!
7
COPYRIGHT©
TESTING STARTS AT THE TOP
COPYRIGHT©
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
8
Trust is good
Control is better
Test is best
“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”
9
COPYRIGHT©
OBJECTIVES OF TESTING, EXAMPLES
Test Design and
Implementation
Test
Environment Set-up
10
Incident
Reporting
Test
Execution
Change
management
Test Completion
Test Monitoring and Control
Test Planning
COPYRIGHT©
THE ITERATIVE DYNAMIC TEST PROCESS FROM ISO
29119
“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.”
11
COPYRIGHT©
MEASURING THE VALUE
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 subprocesses in the scope
12
COPYRIGHT©
TEST STRATEGY FOLLOWS ON FROM TEST POLICY
General :
a)
b)
c)
d)
e)
f)
g)
13
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’
Detailed strategy for
’test sub-process n’
1. Entry and exit criteria
2. Test completion criteria
3. Test documentation
4. Degree of
independence
5. Test design techniques
6. Test environment
7. Metrics to be collected
8. Retesting and
regression testing
1. Entry and exit criteria
2. Test completion criteria
3. Test documentation
4. Degree of
independence
5. Test design techniques
6. Test environment
7. Metrics to be collected
8. Retesting and
regression testing
Test subprocesses may be:
• Acceptance test
• Integration test
• Component test
• Performance
test
• Load test
• etc.
COPYRIGHT©
TEST STRATEGY STRUCTURE FROM ISO 29119
Test Planning
Test Design and
Implementation
Test
Environment Set-up
Test Monitoring and Control
Entry criteria
Test
Execution
Test Completion
14
Exit criteria
COPYRIGHT©
INFLUENCE FROM STRATEGY ON THE TESTING