Scanning the Internet for External Cloud Exposures via SSL Certs
Shirly Ronen - Brainstorming and mind mapping exploratory testing
1. 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.html
First, I have collected some relevant materials from the net. Nice stuff (I have marked their origin so you can explore more
and added my thoughts)
At the second part of this post you'll 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 and
quality 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 one
way 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 our
though 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 more
relevant places.
Visualizing our thought help us elaborate them to be more clear and creative.
As for the agile values, it helps
us share, visualize and
communicate our ideas.
When thinking about the mind
mapping, we can relate this way
of visualizing to almost
everything we do: preparing to
a lecture, planning a trip,
brainstorming and of course,
planning our next testing
session.
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.
3. 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.
4. 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….
5. 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
6. 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
