csaba szökőcs– evosoft hungary kft. · © evosoft hungary kft. 2018 | risk based testing in...
TRANSCRIPT
© evosoft Hungary Kft. 2018 | Risk Based Testing in agile teams 1
Risk Based Testing in agile teamsCsaba Szökőcs – evosoft Hungary Kft.
© evosoft Hungary Kft. 2018 | Risk Based Testing in agile teams 3
© evosoft Hungary Kft. 2018 | Risk Based Testing in agile teams 4
© evosoft Hungary Kft. 2018 | Risk Based Testing in agile teams 5
© evosoft Hungary Kft. 2018 | Risk Based Testing in agile teams 6
24h
Testing in Scrum
Product backlog Sprint backlog Potentially shippable product
Sprint2-4 weeks
Iteration
Testing
© evosoft Hungary Kft. 2018 | Risk Based Testing in agile teams 7
24h
Testing in Scrum
Product backlog Sprint backlog Potentially shippable product
Sprint2-4 weeks
Iteration
Testing
© evosoft Hungary Kft. 2018 | Risk Based Testing in agile teams 8
Planning
Process of Risk Based Testing in agile teams
Preparation Refinement Sprint
New user story
PO
RBTmeeting
What can go wrong with the
story?
Basic risks
• Risk 1• Risk 2• Risk 3
© evosoft Hungary Kft. 2018 | Risk Based Testing in agile teams 9
© evosoft Hungary Kft. 2018 | Risk Based Testing in agile teams 10
© evosoft Hungary Kft. 2018 | Risk Based Testing in agile teams 11
© evosoft Hungary Kft. 2018 | Risk Based Testing in agile teams 12
© evosoft Hungary Kft. 2018 | Risk Based Testing in agile teams 13
© evosoft Hungary Kft. 2018 | Risk Based Testing in agile teams 14
© evosoft Hungary Kft. 2018 | Risk Based Testing in agile teams 15
1 2
© evosoft Hungary Kft. 2018 | Risk Based Testing in agile teams 16
1 2
© evosoft Hungary Kft. 2018 | Risk Based Testing in agile teams 17
Tips for collecting risks
Focus on the user story1 Invite experts
from other teams2
Collect risks, not test cases3 Consider possible
side effects4
Collect risks from different areasNFRs, claims, design decisions, previous bugs, experience, check list
7
Check features in combination5 Participation is
optional6
© evosoft Hungary Kft. 2018 | Risk Based Testing in agile teams 18
Planning
Process of Risk Based Testing in agile teams
Preparation Refinement Sprint
New user story
PO
RBTmeeting
Basic risks
• Risk 1• Risk 2• Risk 3
Groomingmeeting
Extended, prioritized risks
1. Risk 22. Risk 33. Risk 1
Risk priorities
• Probability• Damage• Test effectiveness
Planningmeeting
Develop / Testaccording priorities
DEMO
Defined test cases
1. Risk 22. Risk 33. Risk 1
Test strategy
Focus on critical parts instead of
happy path
What can go wrong with the
story?
© evosoft Hungary Kft. 2018 | Risk Based Testing in agile teams 19
Example: Split screen in Android
© evosoft Hungary Kft. 2018 | Risk Based Testing in agile teams 20
Risk Probability Damage ExposureTest
effectivenessPriority
The Back button closes the wrong application 2 3 6 3 18
The keyboard is active in the wrong application 3 5 15 5 75
Zooming with two fingers does not work 5 2 10 2 20
Sound gets mixed between applications 1 1 1 4 4
Battery goes dead too quickly 4 4 16 1 16
Test-drivenAvoid
side effectsMotivation
More value in tests
Benefits
© evosoft Hungary Kft. 2018 | Risk Based Testing in agile teams 22
OverdoToo much
timeFalse sense of
securityShift
responsibility
Dangers
© evosoft Hungary Kft. 2018 | Risk Based Testing in agile teams 24
Your powerful partner
© evosoft Hungary Kft. 2018 | Risk Based Testing in agile teams 25
Contact
evosoft Hungary Kft.
1117 – Budapest
Kaposvár utca 14-18.
Telefon: +36 (1) 38-16400
Telefax: +36 (1) 38-16101
Csaba Szökőcs
CT RDA DS EU HU OPS 6 3
Mobile: +36 (20) 380-2002
Email: [email protected]
Counterpart