I first learnt about Mind Maps in 2011, however I started using them just recently.
In my current role, I am the sole tester of a team with 7 developers. There are no test cases to work off and no previous notes from the last tester who worked here. The more I learn about a feature I’m testing, the more complicated it gets and it’s hard to keep track of all the things I have tested/need to test.
Because of this, I started using mind maps a few months ago to test new features. My team saw me drawing a mind map in a meeting about a new feature. First one person looked to see what I was doing and before I knew it, the meeting had come to a standstill while everyone in the meeting looked to see what I was writing.
After the meetings, I would sit down and refine the map a bit more before showing it to the developer designing the feature. After explaining what mind maps are and how to read them, the developer would point out things I have missed and suggest more things to test which helped make my mind map more useful in testing. In my previous roles, a developer has never sat down with me to provide their input into areas I should test/have missed.
One day the CEO saw a few mind maps on my desk and took interest. A few weeks later he told me he had downloaded several different mind mapping tools to find a good one. His plan was to purchase a license when he found a good one for the whole company to use.
As a tester who doesn't like using test cases, I find mind maps a perfect alternative for taking down notes. Mind maps provide the same coverage as test cases (if not more) with very little down time writing them.
Mind maps are quick, simple and can be easily updated to fit in with product changes, whereas test cases take hours to create/update and take valuable time away from actual testing.
Add a Comment