Post on 18-Nov-2014
description
© Martin Mussmann and PrettyGoodTesting®
By Martin Mussmann
Mind Maps as part of theAgile Testing Process
1EuroSTAR 2011 : W4A : Mind Maps As Part Of The Agile Testing Process
Who am I?
Test consultant at PrettyGoodTesting
ISTQB certified Test Analyst (adv. level)
4 years of test experience from:• Small teams• Agile projects• Investment Banking
2
Agenda
• Initial test process on the project
• Challenges in an highly dynamic environment
• Different attempts to overcome the challenges
• New test process
• My experiences with mind maps
3
Type of project
Scrum team
Very dynamic business requirements• Sometimes even changing from week to week
Low risk to business
4
Initial test process
Test cases made for ”Man on the street”
5
Week1:Regression testing
Week2-3:Test case design
Week4:Test of new features
Initial project challenges
Changing requirements• Wasted time on test design & test cases• Bugs incorrectly reported
Hard to get developers and business analyststo review test designs• This caused a lot of mis-communication
Test cases hard to maintain• Wasted test ideas• Outdated test cases
6
Old test case example
7
Attempts to overcome challenges
8
Mind maps as test design
9
How do we draw mind maps?
10
Mind map as test case
11
Failed
Passed
New test process
12
Same scrum cycle as development team
Lesson learned
So did we improve quality?
Well hard to tell but we managed to:• Reduce time spend on creating test
design and test cases by a lot• Improved review ability!• Got a lot more time for actual testing!
13
My experiences
More creative test cases!
Test ideas aren’t lost!
Developers asking to see mind maps!
More feedback on review!
Forcing new testers to ask and explore!
Focus on WHAT and NOT HOW to test!
14
Questions and CommentsPlease feel free to contact me
Martin Mussmann
Test Consultant
Mob: (+45) 3163 0212MAMU@PrettyGoodTesting.comLinkedIn: mmussmann@gmail.com
© Martin Mussmann and PrettyGoodTesting®
15EuroSTAR 2011 : W4A : Mind Maps As Part Of The Agile Testing Process