Skip to main content

MindMaps 101

Apologies for the lack of updates, it's been a busy week, had my 3 year wedding anniversary last week, so was busy sorting stuff out for that, and had a bit of a hectic weekend! :)

Anyway, I've recently been reading a lot about mindmaps, and how they are useful when brainstorming and coming up with areas that may or may not need testing when a story/pbi comes in.

I started to wonder what the fuss was about, so I recently created a MindMap for a recent blog post here and found it extremely useful.

So let me go over how they work, and then I'll explain how I personally find them helpful and hopefully you will too.

They are an extremely simple concept, you have your theme in the middle and off of that branches anything that you think is related or want to investigate, and then you can have branches off of them too... And so on... I find that the mind will naturally flow from one area to the next, and you won't have to think too hard and you won't forget important areas.

So let me give a brief example, say you want to discuss performance testing, you could then branch off and discuss why it's important, and then off of that discuss common performance issues. 



As you can see you can branch off a number of times, and can create quite the interesting mindmap. I've seen some with so many points on, for instance this one here around android testing is massive and extremely useful to anyone who wishes to know more about testing on an android device. This illustrates that it doesn't matter how big or how small a mindmap is, it can be useful to you, and will be useful to you and hopefully others will also find it useful and learn something from it.

I currently use bubbl.us but am on the look out for a free version which will allow me to save as much as I want, so if anyone has any suggestions shout :)

I don't use mindmaps all the time for pbis and test planning, as some are so small that it's not necessary, and I'm still quite new to them, so am trying to use them as efficiently as possible, I am using them whenever I think of a new blog post, and I try and share them with you when I can. The one for this blog post is at the bottom of this post... so enjoy! In a future post I'll take an example PBI and come up with a mindmap for it....




Labels:

Comments

  1. Joe Brannan21 May 2013 at 03:39

    I'm very similar - I've seen a lot about mindmaps on twitter, but haven't really used them since university days. Then I came across an example where I thought they might come in useful, thanks to twitter I found the free software 'Freemind' and now have a dozen mindmaps covering a variety of topics.

    ReplyDelete
    Replies
    1. Gareth Waterhouse21 May 2013 at 05:31

      I had a look at FreeMind, and I guess I'll have to play about with it some more in order to understand it's powers fully, but there are definitely tools about there. Bubbls.us was just easy and intuitive to use.

      Delete
  2. Srinivas Kadiyala21 May 2013 at 05:25

    Thanks for sharing the post.

    What is PBI's ?

    ReplyDelete
    Replies
    1. Gareth Waterhouse21 May 2013 at 05:34

      PBIs are Product Backlog Items, they are often a User story, and written in the following context:

      As a User
      I want to have something available to me/some new functionality
      So that I can do something

      They are effectively an item of work that the team will have to work on. Commonly found in an Agile environment. I'll try and write a blog post about them in the future....

      Delete
  3. Phil21 May 2013 at 05:58

    Mindmaps spread - have you seen the 101 from Darren McMillan?

    http://www.bettertesting.co.uk/content/?p=956

    ReplyDelete
  4. Amar G Deogirikar22 May 2013 at 06:33

    Nice one, I have been trying to find out more about "lean and mean" test case design using mind maps techniques, because I am lazy to write detailed long and meaningless test cases. The business requirements where I work change day to day and I need to edit/rewrite test cases frequently. It is a big task to keep up with everything! Is this something you can extend with an example in your future posts! :)

    ReplyDelete
    Replies
    1. Gareth Waterhouse15 July 2013 at 03:44

      There is one in the works! Just been really busy lately!!! Hopefully I can deliver it soon!

      Delete
  5. Unknown10 October 2017 at 02:04

    Great blog. Thank you for sharing. The information you shared is very effective for learners.Keep Updating...

    Best Embedded System Training in Chennai | Embedded Course in Chennai | Embedded Training in Chennai | Best Embedded Training in Chennai | Embedded Systems Course in Chennai | Matlab Training in Chennai | LabVIEW Training in Chennai | VLSI Training in Chennai

    ReplyDelete

Post a Comment

Popular posts from this blog

Coding something simple.... or not! Taking a screenshot on error using Selenium WebDriver

I recently wrote a little function that takes a screenshot at the end of a test if it has errored. What sounded very simple at the start turned out to be quite a bit of work, and quite a few lines of code to handle certain scenarios! It's now over 50 lines of code! I'll start with what I had at the beginning, this was to simply take a screenshot in the working directory, we are using SpecFlow and Selenium to run the tests, so we are going to check if the ScenarioContext.Current.TestError isn't null, if it is, then using Selenium, take a screenshot (note the below code is a simplified version of what I had at the beginning). [AfterScenario]         public static void TakeScreenShotOnError()         {             if (ScenarioContext.Current.TestError == null) return;             var screenshotDriver = Driver as ITakesScreenshot;             if (screenshotD...
15 comments
Read more

How to manage resources within new teams?

Working where I work we are constantly spinning up new teams to take on new workloads as business come up with new demands and new features they want developed and tested. The problem with this is how do we ensure the work of the newly spun up team is of sufficient quality. One method is by taking people from other established teams and placing them on the new team. This works great for the new team, but unfortunately it will oftenl eave the established team lacking in a resource whilst they try and fill the gap left by the person who has left. We are seeing this often with our offshore teams, it can be damaging to the team structure and the teams velocity, but try as I might, I can't think of another way around it. It's far easier to take 1 person from a team that is established than it is to build a whole new team from scratch. At least by leaving the core of a team in place, you should be guaranteeing that the new team are aware of any coding standards or any QA standard...
Post a Comment
Read more

Considerations when creating automated tests

We recently released to a number of teams our automated regression pack that has been worked on over the past few months. This regression pack tests legacy code, but contains a large number of tests.  As a bit of background, a number of teams are working on new solutions whilst some are still working on legacy code. With this in mind we constructed an email with a list of guidelines when creating new tests that need to be added to this regression pack.  I figured that these can be quite broad so should apply for any organisation, so thought it would make an interesting blog post...  So here goes,  when creating automated tests, it's important to consider and adhere to the following: - Think about data . The tests need to retrieve or set the data they need without any manual intervention - This should help them be more robust and easier to run without manual intervention. - The tests need to be idempotent - By making it so that each test is standalone and does...
Post a Comment
Read more