Mindmaps: a Killer Way to Increase Your Test Coverage

Plan your Test Cases with these Seven Simple Steps

MM1

What is a mind map?

A mind map is a diagram used to visually organize information. It can be called a visual thinking tool. A mind map allows complex information to be presented in a simplified visual format. A mind map is created around a single concept. The concept is represented as an image in the center to which the associated ideas are added. Major ideas are connected directly to the central concept, and other ideas branch out from those.
Mind mapping is great for note taking, planning, studying, brainstorming etc. The term “mind map” was first used by Tony Buzan in 1974. In school, I preferred visual mind mapping over traditional note-taking, and it proved to be a great aid to revise and recall the concepts quickly. This is because the information in a mind map is structured in a way that mirrors exactly how the brain functions — in a radial rather than linear manner. A mind map literally maps out your thoughts, using associations, connections and triggers to stimulate further ideas.

How to draw a mind map:

Creating a mind map doesn’t take artistic talent or exceptional creative ability. Just let your brain flow naturally.

Tony Buzan, the father of mind maps, suggests the following steps:

1. Start in the center of a page.

Why? Because starting in the center, gives your Brain freedom to spread out in all directions and to express itself more freely and naturally.

2. Use an IMAGE or PICTURE for your central idea.

Why? Because a picture is worth a thousand words and images help you use your imagination. A central image is more interesting, keeps you focused, helps you concentrate and gives your brain more of a buzz!

3. Use COLORS throughout.

Why? Because colors are as exciting to your brain as images are. Color adds extra vibrancy and life to your mind map. It also adds tremendous energy to your creative thinking, and is fun!
4. CONNECT your MAIN BRANCHES to the central image and connect your second and third level branches to the first and second levels, etc.

Why? Because your brain works by association. It likes to link two (or three, or four) things together. If you connect the branches, you will understand and remember a lot more easily.

5. Make your branches CURVED rather than straight

Why? Because having nothing but straight lines is boring to your brain.

6. Use ONE KEY WORD PER LINE.

Why? Because single keywords give your mind map more power and flexibility.

7. Use IMAGES throughout.

Why? Because images make an impact. Like the central image, all subsequent images are also worth a thousand words. So, if you have only 10 images in your mind map, it’s already equal to 10,000 words of notes!

 

How to use mind mapping techniques in software testing?

MM3

PRO TIPS
If a mind map is getting too big or complicated try splitting it.
Do not use long detailed sentences in mind maps.
Develop your own personal style of mind mapping.
Mind maps can be used in all the test stages from test planning to test case execution.

  • Test Planning
  • Requirement analysis
  • Impact analysis
  • Task allocation
  • Test case design
  • Traceability
  • Test reporting—quick test reports

Test Planning

While test planning, you can draw an initial mind map keeping in mind the list of tasks, schedules, tools, roles, responsibilities, milestones, etc. Present the mind map and discuss it with your stakeholders. Modify the mind map if any changes are required. One thing you will love about mind maps is that they have the flexibility to adapt to changes—simply by adding or removing a node/branch. This flexibility might not happen when you draw on a paper, but a mind mapping software facilitates any changes.The final mind map shows you the scope of testing in one glance. This can be used as a blueprint and later converted into a plan. This ensures that no test activity is missed.

Test case design

Mind maps are an efficient way of creating lean test cases: It reduces the time required for creating test cases that yield better results. Mind maps are very easy to maintain and are flexible to changing requirements.
Draw branches from every user story/epic and associate all its functionalities as sub-nodes. Start adding test ideas/test cases for each functionality.

I created a mind map covering test ideas for major functionality. My team started to expand the mind map by branching out more and more test ideas. We kept adding new nodes when we found unique scenarios that uncovered bugs during our test sessions. This drastically increased our test coverage. The final mind map can be as the basis for a test case document or it’s okay if it’s used as is.

The best part of mind mapping is that you generate more ideas when drawing them. Collaborative mind mapping with the team gives you the best results.

MM4

Traceability mind map

A traceability matrix is an essential tool for every tester to analyze and improvise the test coverage. You can use a mind map instead of a tabular traceability matrix.

To create a traceability mind map:

First add nodes of all the epics. Then, draw branches from every module and associate all its user stories as subsequent nodes. Now, link the test cases for every functionality. You can also link the requirement number of the test management tool. This ensures that you have not missed writing test cases for any user story. This mind map gives you the birds-eye view of your test coverage. You can identify the areas where you need to strengthen your coverage.

You can use mind maps anywhere and everywhere!
Tools

There are tons of commercial and open-source tools that lets you visualize your ideas as a mind map. I prefer the following tools:

Xmind(Windows/Mac/Linux)- Probably the most popular and free mind mapping tool.
Coogle(Web app) – Coogle is a web app that lets your team collaborate and work on a single mind map.

The use of mind maps is becoming popular with agile testers and lean test practitioners. When will you start using mind maps?

 

Prashant Hegde

Prashant is a passionate tester. He currently works as a QA lead in Razorthink software. He leads a small team and ensures that the products he works on meet the highest standards in tight schedules and deadlines. Prashant is a gamer, a biker, and a writer. He writes a blog on best practices in software testing in his spare time. Follow Prashant on his website – prashanthegde.in.

Prashant Hegde
Prashant is a passionate tester. He currently works as a QA lead in Razorthink software. He leads a small team and ensures that the products he works on meet the highest standards in tight schedules and deadlines. Prashant is a gamer, a biker, and a writer. He writes a blog on best practices in software testing in his spare time.

The Related Post

Introduction This article discusses the all-too-common occurrence of the time needed to perform Software Testing being short changed as specification, development, and unforeseen “issues” cause the phases prior to testing to expand. The result is that extreme pressure is placed upon the testing organization to perform the testing function within a reduced time frame. The ...
This article first appeared in BETTER SOFTWARE, May/June 2005. Executives and managers, get your performance testing teams out of the pit and ahead of the pack Introduction As an activity, performance testing is widely misunderstood, particularly by executives and managers. This misunderstanding can cause a variety of difficulties-including outright project failure. This article details the ...
  Explore It! is one of the very best software testing books ever written. It is packed with great ideas and Elisabeth Hendrickson’s writing style makes it very enjoyable to read. Hendrickson has a well-deserved reputation in the global software testing community as someone who has the enviable ability to clearly communicate highly-practical, well-thought-out ideas. ...
This article was developed from concepts in the book Global Software Test Automation: Discussion of Software Testing for Executives. Introduction When thinking of the types of Software Testing, many mistakenly equate the mechanism by which the testing is performed with types of Software Testing. The mechanism simply refers to whether you are using Manual or ...
Last week I went to StarWest as a presenter and as a track chair to introduce speakers. Being a track chair is wonderful because you get to interface more closely with other speakers. Anyway…one of the speakers I introduced was Jon Bach. Jon is a good public speaker, and I was pleasantly surprised that he ...
Introduction Software Testing 3.0 is a strategic end-to-end framework for change based upon a strategy to drive testing activities, tool selection, and people development that finally delivers on the promise of Software Testing. For more details on the evolution of Software Testing and Software Testing 3.0 see: The Early Evolution of Software Testing Software Testing ...
Jeff Offutt – Professor of Software Engineering in the Volgenau School of Information Technology at George Mason University – homepage – and editor-in-chief of Wiley’s journal of Software Testing, Verification and Reliability, LogiGear: How did you get into software testing? What do you find interesting about it? Professor Offutt: When I started college I didn’t ...
One of the most dreaded kinds of bugs are the ones caused by fixes of other bugs or by code changes due to feature requests. I like to call these the ‘bonus bugs,’ since they come on top on the bug load you already have to deal with. Bonus bugs are the major rationale for ...
When You’re Out to Fix Bottlenecks, Be Sure You’re Able to Distinguish Them From System Failures and Slow Spots Bottlenecks are likely to be lurking in your application. Here’s how you as a performance tester can find them. This article first appeared in Software Test & Performance, May 2005. So you found an odd pattern ...
Creative Director at the Software Testing Club, Rob Lambert always has something to say about testing. Lambert regularly blogs at TheSocialTester where he engages his readers with test cases, perspectives and trends. “Because It’s Always Been Done This Way” Study the following (badly drawn) image and see if there is anything obvious popping in to ...
They’ve done it again. Gojko Adzic, David Evans and, in this book, Tom Roden, have written another ‘50 Quick Ideas’ book. And this one is equally as good as the previous book on user stories. If not even better.  
For mission-critical applications, it’s important to frequently develop, test, and deploy new features, while maintaining high quality. To guarantee top-notch quality, you must have the right testing approach, process, and tools in place.

Leave a Reply

Your email address will not be published. Required fields are marked *

Stay in the loop with the lastest
software testing news

Subscribe