Shirly Ronen - Brainstorming and mind mapping exploratory testing

Mind Mapping for exploratory testing The most intuitive testing way of thinking. Shirly Ronen –Harel shirly@agilesparks.com http://www.the-organic-mind.com/how-to-mind-map.htmlFirst, I have collected some relevant materials from the net. Nice stuff (I have marked their origin so you can explore moreand added my thoughts)At the second part of this post youll find aslo comments and how does this look in reality.Mind mapping the testing exploratory session is a useful, visible natural tool that may shorten and focus testing session.It also answers some of the agile values of visibility and collaboration and actually results with a good testing andquality focus, using the entire team and our natural way of thinking.Mind Mapping is a thinking tool and a thinking approach. Its a Very basic and natural way of thinking and actually, in oneway or another used by all of us naturally.Mind map just place our thought in a very simple and visible form.Nothing new for our brain, just for our eyes. It helps us clear our mind of waste, of overload. Helps us see clearly ourthough and helps us change or view according to our needs.Once we can "read" our mind, we can better follow the details, the path and prepare to move to more proper and morerelevant places.Visualizing our thought help us elaborate them to be more clear and creative.As for the agile values, it helpsus share, visualize andcommunicate our ideas.When thinking about the mindmapping, we can relate this wayof visualizing to almosteverything we do: preparing toa lecture, planning a trip,brainstorming and of course,planning our next testingsession. http://www.the-organic-mind.com/how-to-mind-map.html The mind map benefit, then, looks like a perfect solution for testing planning as well. Many testers are naturally tuned to these techniques. I urge testers to get back to their natural way of thinking. I know you do that. We all know that a good tester takes out a pen and a paper and draw their tree of tests. It happens when they plan a bug fix tests or whatever a small and fast change introduced. But since they were thought to document, plan ahead, xls their thought, the nature intuitive testing tree, got forgotten or forbidden. Then why not using the mind map out in the open? The key to getting the maximum value is to establish a good technique and be prepared to experiment. The mind map will only give testers one more tool to do what they do naturally any way.

What is exploratory testing anyway?"A testing mindset involving simultaneous learning, test design & test execution." (James Bach, ”Exploratory TestingDefined” - ET Workshop v. 1.20 - Test Management ; ©2002 Amland Consulting) 1) Charter- Brief information / guidelines on: Mission: Why do we test this? What should be tested? How to test (approach)? What problems to look for? Might include guidelines on: Tools to use Specific Test Techniques or tactics to use What risks are involved Documents to examine Desired output from the testing 2) Time Box Short: 60 minutes (+-15) Normal: 90 minutes (+-15) Long: 120 minutes (+-15) From Rapid Software Testing, copyright © 1996-2002 James Bach 3) Reviewable Result Charter #AREAS Start Time Tester Name(s) Breakdown #DURATION #TEST DESIGN AND EXECUTION #BUG INVESTIGATION AND REPORTING #SESSION SETUP #CHARTER/OPPORTUNITY Data Files Test Notes Bugs #BUG Issues #ISSUE (From Rapid Software Testing, copyright © 1996-2002 James Bach ) 4) Debriefing The manager reviews session sheet to assure that he understands it and that it follows the protocol. The tester answers any questions. Session metrics are checked. Charter may be adjusted. Session may be extended. New sessions may be chartered. Coaching / Mentoring happens. (From Rapid Software Testing, copyright © 1996-2002 James Bach )(Lyndsay, James and Eeden, Niel van, 2002, “Adventures in Session-Based Testing”, paper at StickyMinds.com presented atEuroSTAR 2002 )

How can mind map be related to the exploratory testing. Practical steps : 1. Charter- Brief information – brainstorm yourself and the team and build the initial mind map Use the aboard and draw the mind map options: Consider: test types, test data, test tools and whatever is in the checklist above.…… Map the relationships between the ideas or key points using lines, arrows, colors and words to link them. Identify the type of relationship between branches : similarity/cause/effect Write these along the linking lines. Arrange items in a logical order to create the structure of your assignment. Decide on the area of tests for each team member. 2. Time Box Perform the selected items tests and approach of the mind map. Elaborate the mind map, add tree branches to whatever is a test, add your path of testing, and add more branches if you find more ways of tests. The elaboration of the mind map never stops, whenever you have an idea – add it to the map. It will be used for the briefing session and may produce new paths of important tests. 3. Reviewable Result Review the mind map with the team. (its visual any way) 4. Debriefing Review session sheet to assure that he understands it and that it follows the protocol. Those who performed the tests answer any questions. Decide on the next session. Talk about the issues raised. Add issues and branches to the map if needed.End of testing: Decide which output and inputs needs to be documented , added as defects to the system, what tests needs to be added to testing repository (automated or manual) Save the mind map for further use in the next exploratory session. To get the most out of mind mapping exploratory, use the entire team to explore and mind map the team testing.

How does this look in reality? Team members are building the mind map together. They are mapping the testing options into a mind map in an open discussion: Open Discussion Sharing Visibility Marking high priority issues Dropping suddenly non important issues Marking rollback issues….

Selecting branches for session (developers & testers) Just before starting the testing, Testers explains developer the scope and testing related issues. Selected issues for testing are marked on the board , with their results status

Failed tests and bugs are marked on the board • Implementing exploratory as a techniques for young teams to integrate testers into the team. › The testing information is shared. › Bugs are shared and visible › Limiting the bugs in progress and reported WIP › Testers are communicating with the entire team. › The big picture is visible for testers. › The development are aware of testing tasks , effort and extent. › The tester gets the chance to lead the team towards quality

Read more about exploratory and mind mapping© Illumine Training. All rights reserved. www.illumine.co.uk info@illumine.co.uk +44 (0)1753866633ET Workshop v. 1.20 - Test Management , ©2002 Amland Consultinghttp://www.the-organic-mind.com/how-to-mind-map.html

http://www.agilesparks.com	967
http://agilesparks.com	75
http://www.slideshare.net	11
url_unknown	4
http://www.agilesparks.co.il	1
http://agilesparks.co.il	1

Shirly Ronen - Brainstorming and mind mapping exploratory testing

by AgileSparks on Apr 15, 2011

Accessibility

Categories

Tags

Upload Details

Usage Rights

6 Embeds 1,059

Statistics

Shirly Ronen - Brainstorming and mind mapping exploratory testing — Document Transcript