What do you do when you must go back to
"basics” in the test management book ?
Testers without test experience combined with limited or missing requirements
Øyvind Woll – Senior Consultant, Vivento AS
“The best training is the training you
actually do”
Oddvar Brå
Legendary Norwegian Cross country skier
“The best testing is the testing that is actually performed”
AGENDA
01
A realistic test strategy
02
The establishment of the test organization
03
Working with integrations and risk components
04
The process of documenting the business processes
05
Synergies between the test process and educating the end users
The Project
•
•
•
•
•
Off the shelf solution – Receive project
Public sector - Healthcare
Large organization - 4000 end users
Nurses, doctors, social workers, executive officers
Migration of sensitive data from existing system
Some of the challenges
• Immature test organization
• Limited test basis quality
• Limited availability of domain knowledge
• Limited time
Inputs to the test strategy
Quality of Test
Basis
•
•
•
RED: Low
AMBER: Medium
GREEN: High
01
A realistic test strategy
Availability
of Resources
The test strategy
• Testdesign – keep it simple but adjust to different
groups of testers
• Test reporting – keep it simple but keep it updated
• Test coverage – risk based – happy path first
• Business processes documentation – keep it
simple and visual
01
A realistic test strategy
The test process
02
Establishment of the test
organization
Introduce the
project team to
basic test
knowledge
05
Test the system and educate the end
users
Test the business
processes
individually – low
level
01
A realistic test strategy
03
Work with integrations and risk
components
Work with the
integrations
04
Document the
business processes
- low level
04
Document the business processes
Document the
business processes
- high level
04
Test the business
processes - high
level e2e
The test levels
Integration
Level
Integrations
01
A realistic test strategy
System
Integration
Level
Risk
Components
User
acceptance
Level
Business
processes
Business
processes
End to end
Processes – No
access control
Business
processes - Actual
access control
The test plan
User
Acceptance
test
Document
Business
processes Low Level
Basic test
training
Test LearnUpdate
System
Integration
test-execution
01
A realistic test strategy
Integration
test
Document
Business
processes High Level
Week
What
Who
1
Test training
Functional domain
experts
2-6
Integration test (TestLearn-Update)
Technical team
2-6
Document business
processes – High level
Functional domain
experts
4-6
Document risk
components
Functional domain
experts/Technical
team
6-8
System Integration test
(Test-Learn-Update)
Functional domain
experts/Technical
team
8 - 11
Document business
processes – Low level
Functional domain
experts
11 – 16
User Acceptance test
(Test-Learn-Update)
End users
Establish the test organization – Test-training
• Talk about the test prosess and why we test
– Motivate the entire project organization("what´s in it for us?")
• Teach and train the test resources in only specific test tasks
– How to extract test conditions – Test analyses
– How to record test results and defects using a test tool
– How to participate in the defect process
Keep it simple, but repeat the How to often and
the Why in every project meetings!
02
The establishment of the test organization
Establish a test framework
• Develop templates for Importing requirements and tests to the test
administration tool
• Develop templates for collecting test conditions from functional
domain experts
• Prepare the test tool for reporting
– Prepare to report on requirement coverage
– Prepare to report on test progress
• Work with test design
– Plan to design high level tests for business process testing
– Plan to design exploratory test sessions for risk components testing
– Plan to design specification based tests for integration testing
02
The establishment of the test organization
Requirements
Hierarchy
02
Requirements - Coverage
The establishment of the test organization
Test condition
template
Templates and test design
Test case template
UAT test result
template
02
The establishment of the test organization
Work with integrations and Risk components
• Workshops with functional domain experts
• Look for interesting test conditions to test
– The most important integrations
• Technical resources and specialists from outside the project
– Functional risk components
• Domain experts
– Non-functional risk components
• Technical resources
03
Working with integrations and risk components
Work with integrations and Risk components
Risk Components
Risk matrix
03
Working with integrations and risk components
Document the business processes - Strategy
• Establish the right level of detail for documenting
business processes visually
• Categorize the business processes into business areas
• Plan and execute workshops on each business process
• Make the business processes testable for the end users
by writing step-by-step guides
04
The process of documenting the business processes
Business
areas
Documenting the business processes
High level
documentation
Low level
documentation
04
The process of documenting the business processes
Learning by documenting business processes
Test basis developed during the test
process
High level business
processes
documented
05
Low level business
processes
documented
Synergies between the test process and educating the end users
The new
system is
Learned
Functional design
adjusted
Learning by testing
Test basis used in training users
Tested end to
end by
Functional
domain
experts
05
The new
system is
learned
Synergies between the test process and educating the end users
Low level
process
documentati
on adjusted
Low level
process
documentation
used in training
end users
The new
system is
learned
Lessons learned
• Focus on testing business processes end to end –
not only functionality
• Focus on test conditions – not test steps
• Focus on low level user documentation – not test
cases