Successfully reported this slideshow.
Your SlideShare is downloading. ×

Software Testing Using Mindmap Technique

Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Loading in …3
×

Check these out next

1 of 44 Ad

More Related Content

Slideshows for you (20)

Similar to Software Testing Using Mindmap Technique (20)

Advertisement

Recently uploaded (20)

Software Testing Using Mindmap Technique

  1. 1. MIND MAPPING Ways To Make Testing More Fun Vijay Nadeshan
  2. 2. What you can expect? 1. Warming Up 2. An approach towards test design 3. What is a mindmap? 4. Why mindmap is required? 5. Where mindmap can be used? 6. Mind-mapping in software testing.
  3. 3. Warming up with 'What is' stuff 1. What is testing? 2. What is test strategy? 3. What is test case?
  4. 4. What is Testing? Testing is the process of evaluating a product by learning about it through exploration and experimentation, which includes questioning, study, modeling, observation, inference etc.
  5. 5. What is Test Strategy? To simplify the process of testing a software application, team of testers plan a test strategy, which defines the testing approach that will be used to test the software. • Determine objectives and scope of testing. • Identify the types of test required. • Tools used for testing. • Plan the environment, test bed, test data and other infrastructures.
  6. 6. What is Test Case? A test case is one particular instance or variation of a test idea. - James Bach
  7. 7. An approach towards Test Design There are two different approach a tester can design the tests: 1. Easy approach 2. Not so difficult approach
  8. 8. PROBLEMS INFORMATION OVERLOADED FORGETTING IMPORTANT INFORMATION INABILITY TO SOLVE COMPLEX PROBLEMS LACK OF CREATIVE THOUGHT LACK OF CLARITY AND DIRECTION LESS PRODUCTIVE LACK OF FOCUS FAILING TO SEE IMPORTANT ISSUES MISSING OUT TASKS MAKING BAD DECISIONS
  9. 9. What is a mindmap? • A mind map is graphical way to represent ideas and concepts. • It is a visual thinking tool that helps structuring information, helping you to better analyze, comprehend, synthesis, recall and generate new ideas. • In terms of testing, a mind map is your understanding of the product.
  10. 10. Why mindmap is required? • Too many problems coming in, it becomes difficult to manage it. • Less time to test, so cannot indulge too much in documents and maintaining them. • Increase test coverage. • Tester can think, steps are spoon feeding. • It enhance productivity. • It uses tree based graphical structure which imprints better on brain than tabular structure.
  11. 11. History of Mindmap
  12. 12. 1950's Allan M. Collins (American Cognitive Scientist) * Network semantics * Father of modern mapping 1960's Tony Buzan (British Psychologist) * Coined the word "MINDMAP" * Popularized the concept of Mind Map 3rd Century BC Porphyry of Tyros (Greek Philosopher) * Using mind mapping to form his ideas making learning easier for the others. * Graphically visualized and organised Aristotle's work
  13. 13. HOW TO DRAW A MINDMAP?
  14. 14. TOOLS XMIND FREEMIND COGGLE MINDMEISTER MINDMUP SIMPLEMIND
  15. 15. 1. START IN THE CENTER OF A PAGE
  16. 16. 2. USE AN IMAGE OR PICTURE FOR YOUR CENTRAL IDEA
  17. 17. 3. CONNECT YOUR MAIN BRANCHES TO THE CENTRAL IMAGE AND CONNECT YOUR SECOND AND THIRD LEVEL BRANCHES TO THE FIRST AND SECOND LEVELS.
  18. 18. 4. ONE KEYWORD PER LINE
  19. 19. 5. USE COLOURS THROUGHOUT
  20. 20. 6. MAKE YOUR BRANCHES CURVED RATHER THAN STRAIGHT-LINED
  21. 21. 7. USE IMAGES THROUGHOUT
  22. 22. MIND MAP GUIDELINES
  23. 23. USES FOR MINDMAPS • Brainstorming • Note taking during a meeting / MOMs • Presentations • Problem Solving • Decision Making • Organization • Company Structure • Team Collaboration
  24. 24. HOW TO USE MINDMAPS IN TESTING? Mind maps can be used in all the test stages from test planing to test case execution. Mind maps can be used for: • Test planning • Requirement analysis • Impact analysis • Task allocation • Review requirements • Test case design • Traceability • Test reporting - Quick test reports
  25. 25. STANDARD FOR TESTING DOCUMENTATION • Time intensive • Bulky • Inflexible structure • Go out of date • Expensive to Maintain • High cost to review • Cumbersome reporting
  26. 26. LEAN TEST ARTIFACTS USING MINDMAPS • Easy to create • Light weight • Assist the rapid paced development • Easy to modify / maintain / review • Adaptable to any development methodology • Triggers creative thought • Quick visual status - reporting
  27. 27. TEST PLAN • Test plan identifier • Introduction • Test Items • Features to be tested • Features not be tested • Test approach • Test pass / fail criteria • Test deliverables • Environments needs • Responsibilities • Staff & training needs • Test Schedule • Risks & Contingencies • Approvals
  28. 28. SIMPLE TEST PLAN 1 IN SCOPE / NOT IN SCOPE
  29. 29. SIMPLE TEST PLAN 2 5W's (WHAT, WHEN, WHY, WHO & WHERE)
  30. 30. TEST DESIGN USING MIND MAP
  31. 31. MNEMONICS SFDIPOT (San Francisco Depot) Test Strategy Heuristics by James Bach Structure, Function, Data, Integrations, Platforms, operations, Time RCRCRC Regression Testing Heuristics by Karen N. Johnson Recent, Core, Risk, Configuration, Repaired, Chronic
  32. 32. RCRCRC Recent, Core, Risk, Configuration, Repair , Chronic
  33. 33. YOU CAN USE MIND MAPS ANYWHERE AND EVERYWHERE
  34. 34. EVEN TO PLAN YOUR WEDDING
  35. 35. MY TO DO LIST
  36. 36. REFERENCES http://www.mindmapping.com/theory-behind-mind-maps.php http://testerstrek.blogspot.com/ http://apps.testinsane.com/ http://www.qualityperspectives.ca/resources/#mnemonics
  37. 37. Questions? Comments? Suggestions?

×