A Taste of Exploratory Testing


Published on

An introduction to Exploratory Testing by Anne-Marie Charrett

Published in: Technology
  • Be the first to comment

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

A Taste of Exploratory Testing

  1. 1. A TASTE OF EXPLORATORY TESTING Anne-Marie Charrett @charrett Skype: Charretts Blog: Mavericktester.com This work is licensed under the Creative Commons Attribution- NoDerivs 3.0 Unported License. To view a copy of this license, visit http://creativecommons.org/licenses/by-nd/3.0/. copyright ©TestingTimes 2013
  2. 2. IRISH CREDENTIALS• Born in St Michaels Dun Laoghaire• Lived in Dublin and Leixlip (officially Co.Kildare)• Studied at Kevin Street, DIT• Worked for EOLAS, Government Standards Body• Holidays, in County Kerry. copyright ©TestingTimes 2013
  3. 3. UNPREDICTABLE CLIMATE• “When all is said and done, the weather and love are the two elements about which one can never be sure.” Alice Hoffman copyright ©TestingTimes 2013
  4. 4. IMPROVISATION copyright ©TestingTimes 2013
  5. 5. copyright ©TestingTimes 2013
  6. 6. CONCLUSIONIRISH MAKE THE BEST TESTERS copyright ©TestingTimes 2013
  7. 7. A TASTE OF EXPLORATORY TESTING Anne-Marie Charrett copyright ©TestingTimes 2013
  8. 8. TEST COIN FLIP FREE Any questions? copyright ©TestingTimes 2013
  9. 9. DISCUSSION• What bugs did you find?• What do you do ? copyright ©TestingTimes 2013
  10. 10. BUGScopyright ©TestingTimes 2013
  11. 11. WHAT DID YOU DO?• Played around• Tried out different things• Figured out how it worked• Saw something unusual - looked more• Read up the information (on Website)• Compared your findings copyright ©TestingTimes 2013
  12. 12. SCRIPTED TESTINGRequires a tester to be able to: Often has formalised methodology based on IEEE829 Design Test Scripts upfront against Requirements Requires Experienced Test Analyst Vs Tester Indicate Expected Result upfront Complete when 100% Test Executed Aims to be repeatable Agile - > automated checking copyright ©TestingTimes 2013
  13. 13. SCRIPTED TESTINGDocumentsTest Strategy Test Spec Test Execution Test ReportActivities Strategy Analysis Design Testing Reporting Modelling Configuration Modelling Configuration Operation Decision Making Operation Observation Observation copyright ©TestingTimes 2013copyright ©TestingTimes 2013 Evaluation Evaluation Communication
  14. 14. “Exploratory testing is an approach to software testing that is concisely described as simultaneous learning, test design and test execution.” Cem Kaner “The plainest definition of exploratory testing is test design and test execution at the same time.” J. Bach copyright ©TestingTimes 2013
  15. 15. SIMULTANEOUSLearningDesignExecution copyright ©TestingTimes 2013
  16. 16. EXPLORATORY TESTING Learning StrategyActivities Modelling Decision Making Configuration Testing Operation Observation Design Evaluation copyright ©TestingTimes 2013
  17. 17. TESTER CENTRIC Learning Autodidactic Self Awareness Autonomy Responsibility CourageTesting Design copyright ©TestingTimes 2013
  18. 18. MYTH #1Exploratory Testing is unstructured copyright ©TestingTimes 2013
  19. 19. copyright ©TestingTimes 2013 Jason Darge
  20. 20. PROBLEM SOLVING STRATEGIES copyright ©TestingTimes 2013
  21. 21. ALGORITHMS• Explicit• Repeatable• Context less important• Knowledge but not skill copyright ©TestingTimes 2013
  22. 22. PROBLEM SOLVING STRATEGIESHeuristicsA heuristic is a falliblemethod of solving aproblem or making adecision.• Requires Skill• Context Dependent The essence of heuristics: http://www.satisfice.com/blog/archives/462• Less Visible copyright ©TestingTimes 2013
  23. 23. EXPLORATORY TESTING HEURISTICS• FEW HICCUPS (Ways to Recognise Bugs) - Michael Bolton• SFDIPOT (Ways to Model and generate test ideas) - James Bach• Heuristic Test Strategy Model - James Bach• http://www.qualityperspectives.ca/resources_mnemonics.html copyright ©TestingTimes 2013
  24. 24. MYTH #2You can’t use documents in Exploratory Testing copyright ©TestingTimes 2013
  25. 25. IS DOCUMENT A DIRTYWORD IN EXPLORATORY TESTING? copyright ©TestingTimes 2013
  26. 26. Documents are great for? Reflective Tool Keeping Track of what we doSharing Information with Others copyright ©TestingTimes 2013
  27. 27. REPORTING• Bug Reports• Test Reports• Mind Maps• Wiki• Conversations• MiPs• copyright ©TestingTimes 2013 Charters and SBTM
  28. 28. copyright ©TestingTimes 2013
  29. 29. copyright ©TestingTimes 2013
  30. 30. SBTM• Session is the basic testing work unit• Each session is chartered• ~ 90 minutes• DebriefRead about it here: http://www.satisfice.com/sbtm/ copyright ©TestingTimes 2013
  31. 31. SESSION SHEET FORMAT• Session charter (includes a mission statement, and areas to be tested)• Tester name(s)• Date and time started• Task breakdown• Data files• Test notes copyright ©TestingTimes 2013 Issues
  32. 32. What valueam I offering bydocumenting this? copyright ©TestingTimes 2013
  33. 33. COBWEB• Challenge Documentation• On the Light side• Begin by Thinking, then read• Where possible, speak• End by date ? (best before date)• Byproducts not end results (its not an end its a means) copyright ©TestingTimes 2013
  34. 34. QUESTIONS? copyright ©TestingTimes 2013
  35. 35. THANK YOU!amcharrett@testingtimes.com.au @charrett Skype: charretts copyright ©TestingTimes 2013
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.