Wednesday, 18 May 2011

Creating Test Case Maps: Where Do I Begin?

In the comments below on my first post I was asked "What do you do with multiple test cases and/or test cases with multiple steps?". The answer is that you split them up and make individual maps. But where and how do you start?

The first step is to create a Feature Map. A Feature Map highlights all of your main areas for testing at a very high level. For examples going forward I have decided to write test cases for a generic web browser so that you can easily follow along. 

For my team, I have found that group test case writing has been very successful. We met as a team and first came up with the main areas of testing. 

For a web browser your Feature Map may look something like this.

Mind Maps are a great way to brainstorm your ideas and are very visual. With some work your team can come up with a good set of main features. You will notice ideas start flowing more naturally, which will lead to more test cases and therefore better coverage. 

Next I have had success with dividing up the main nodes into individual Area Maps. In this case we would have maps for Setup, Options, Bookmarks, History, Controls and Window. Split the work among the team and have each take one Area (an Area being a group of common test cases) to start expanding and writing test cases. 

A tester may go off and create a map for Bookmarks such as shown here. 

I suggest printing this map off or display on a projector for your team to discuss. Get everyone up to talk about the test cases and find out what is missing.

There is one map created per Area. If you find a map is getting too large, split it into sub maps. Think of User Stories in Agile. Sometimes we have to split them up to make them easier to manage. The same concept applies to Area Maps.

Next post will talk about test case execution and how to report on results. Again, this is at a very high level at the moment. We will go into more details about formatting, priorities, how to include detailed information, etc at a later point.

Please let me know if you have any questions or if there is something you want me to cover. The more, the better :) I want to learn just as much as you do. 


  1. It's good to see that someone else maps this way, too - this is how I come up with the high-level design of test cases as well.

    I'll be watching for your post on execution; I think there are some ways I can improve my own process, as I essentially use the map as a guide for exploratory testing when I receive a new feature.

  2. Thanks for giving an insight. This is a very illustrative example

  3. A very good idea. We have been following this as well in our teams and it is helping us. Are you generating maps for all the combinations as well?

  4. A very good idea. We have been following this as well in our teams and it is helping us. Are you generating maps for all the combinations as well?

  5. Wow, I had no idea that anyone was still reading this blog :) Unfortunately my new place is not using Agile development practices and I don't get to play with mindmaps as much as I used to. I know a few companies in my area though that are fully engaged with using maps for test case plans with great success.