This document discusses how a team at Infragistics uses mind maps to support exploratory testing. The team builds a mind map for each new feature to identify test conditions, ideas, and variables to cover. Mind maps help the team iterate over existing test ideas, identify new test conditions and ideas, and maintain a common understanding of features. The team references mind maps during exploratory testing sessions but does not track the sessions in the maps. Mind maps are updated based on product changes and stored in a repository with naming conventions. The approach helped the team share knowledge and avoid rethinking test ideas from scratch.
3. WORK EXPERIENCE
• Senior Quality Engineer, Infragistics, 2009
• TestingUy - www.testinguy.org
ABOUT ME
STUDIES
• Computer Engineer
• Certified Scrum Master
• Rapid Software Testing course with Michael Bolton
• Association for Software Testing courses
(Foundations & Bug Advocacy)
• ISTQB Foundation
• …
PAST WORK EXPERIENCE
• Test Manager, Tester, Business Analyst
• Teacher for Computing Science Department within the
School of Engineering at Universidad de la República
@claubs_uy
6. THE PRODUCT UNDER
TEST
• In the market since 2012
• Nine major releases, several
intermediate updates and silent
updates
7. • Developers (7)
• Visual designers (1)
• Interaction designers (1)
• Technical writer (1)
• Testers (1)
THE TEAM
Testing is
performed by
most of us
9. CHECKLISTS
• Test ideas and variables to cover
• Kinds of errors we were looking for
• Solutions risks
• Known issues and decisions
10. • Writing checklists with the feature developers helped identify testing variables
from inside the code
• The testing variables and ideas to cover were explicitly shared by the team
• It was difficult to represent dependent test variables
CHECKLISTS
• It was difficult to see the big picture of what we were modeling
24. • Emphasize related test ideas
• Use symbols, notes and colors
• Represent cross-feature test conditions and
dependencies
GUIDELINES & STRUCTURE
CONVENTIONS TO
We defined a ‘meta language’ to
elaborate our mind maps
35. • Iterate over existing test ideas
• Identify test conditions and ideas better
• Have a common understanding of the features
• Share knowledge
MIND MAPS HELP US
36. George E. P Box
All models are wrong,
but some of them are useful
38. Useful links for further reading
• Heuristic Testing Strategy Model by James Bach
http://www.satisfice.com/tools/htsm.pdf
• Using Mind Maps to Document Exploratory Testing by Samuli Lahnamäki
https://www.stickyminds.com/presentation/using-mind-maps-document-exploratory-testing
• Explore It!: reduce risk and increase confidence with Exploratory Testing by Elisabeth Hendrickson
https://www.amazon.com/Explore-Increase-Confidence-Exploratory-Testing/dp/1937785025/
• Essential mind mapping: Rapid test design by Darren McMillan
http://www.bettertesting.co.uk/content/?p=1438
• Part 1: using mind-mapping software as a visual test management tool by Aaron Hodder
http://assurity.co.nz/community/big-thoughts/part-1-aaron-hodder-on-using-mind-mapping-software-as-a-visual-
test-management-tool/
• Part 2: using mind-mapping software as a visual test management tool by Aaron Hodder
http://assurity.co.nz/community/big-thoughts/part-2-aaron-hodder-on-using-mind-mapping-software-as-a-
visual-test-management-tool/
• When the whole team owns testing: Building testing skills by Lisa Crispin
http://lisacrispin.com/whole-team-owns-testing-building-testing-skills/
• Resources on Exploratory Testing, Metrics, and Other Stuff by Michael Bolton
http://www.developsense.com/resources.html