XMind

Mind Maps as part of the agile testing process

1. Conclusion

   1. More creative test cases

   2. More focus on end result than document creation

   3. It is a question list

      1. Not a step by step guide

   4. It has created a culture where programmers are asking to see the maps

   5. Forcing testers to ask and explore

   6. Focus on WHAT not HOW

2. Speaker: Martin Mussmann (Pretty Good Testing)

3. Old testing process was for "man on the street" - anyone could run them

   1. "I wrote it, so it must be true" <-- about test cases

4. Classification tree worked initially

   1. But people didn't always understand it

5. Mind Mapping

   1. Draw them how they should be drawn

      1. how you feel they should be

   2. Collapse and Expand when showing the people

      1. i.e. hide / show details as required

   3. Moves Testing away from step based rote, to Testers needing some product knowledge

   4. Test Design > review > Feedback > No need for further test creation - mind map is the Test Case

   5. Colour coding on mind map (green - tested, red - failed)

   6. Regression Testing

      1. Clear the colour coding

         1. Start again

   7. Add notes for further contextual meaning

   8. This process KILLED the Test Team

      1. A Tester is now in the Development Team

         1. No creating/editing of Test Cases

      2. Reduced time of documentation creation

   9. Improved review process