Exploratory Testing As A Quest

1,621 views

Published on

Published in: Technology, Business
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,621
On SlideShare
0
From Embeds
0
Number of Embeds
553
Actions
Shares
0
Downloads
39
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

Exploratory Testing As A Quest

  1. 1. Exploratory Testing … enjoy the Quest Exploratory Testing Class Meeting #1
  2. 2. Definition Exploratory testing is simultaneous learning, test design and test execution Unlike the scripted testing, here the tester actively controls the design of the tests as those tests are performed, and uses information gained while testing to design new and better tests.
  3. 3. Ad-hoc vs Exploratory Exploratory means: thoughtful focused disciplined accurate “ accomplishing mission” Ad-hoc sounds like: random chaotic uncontrollable careless “ wandering around”
  4. 4. Exploratory testing is a Quest <ul><li>Think of any Quest game you ever played. </li></ul><ul><li>You have a mission, and a set of tools to accomplish it. </li></ul><ul><li>You have no idea on what’s going to happen next. But all your further steps will depend on that. </li></ul><ul><li>It is not easy to solve Quests, it requires logical thinking, observation, accuracy and lot of patience sometimes... </li></ul>
  5. 5. Before we start our class… <ul><li>Is that possible to learn being a better explorer? </li></ul><ul><li>Is that possible to learn being a better Quest-solver? </li></ul>Yes. But not through THEORY . The only way is PRACTICE .
  6. 6. Structure Tester Mission Product ET Time [Quest] + Reporting!
  7. 7. Test design. The ideas. <ul><li>Exploratory tester designs tests ‘on the fly’. </li></ul><ul><li>Instead of randomly clicking he first thinks of possible tests. Tests for systematical exploration of the product. </li></ul><ul><li>Quest player has many-many steps and combinations he may try. But experienced player knows immediately which of them have sense in the current situation. </li></ul>
  8. 8. Authorization functionality Ability to design tests is predicting what may go wrong and selecting strong test data to check it
  9. 9. Test idea How about trying to pass some invalid data, looking as valid?..
  10. 10. Test data How about trying to pass some invalid data, looking as valid?..
  11. 11. Test case How about trying to pass some invalid data, looking as valid?..
  12. 12. Success! Bug in security system!
  13. 13. Observation. Details matter. <ul><li>Exploratory tester is always looking for symptoms. Anything unusual may mean a problem. </li></ul><ul><li>Quest player starts every new screen from observation. Every clickable item may help him in resolving the puzzle. Even the tiniest detail is crucial here. </li></ul>
  14. 14. For the novice player this screen doesn’t say much. The only way is go clicking here and there…
  15. 15. But an expert will notice important details (even the smallest once) right away!
  16. 16. Moreover, expert player will notice interesting connections between things...
  17. 17. Critical thinking. <ul><li>Exploratory tester should be able to review and explain his logic, looking for errors in his own thinking. </li></ul><ul><li>Quest player bases his strategy on assumptions and ideas. But when he gets stuck he has to re-think his ideas to be able to move on. </li></ul>
  18. 18. Sometimes to go forward you must go back first. I must have missed something... ???
  19. 19. Diverse ideas. <ul><li>Exploratory tester needs to produce many testing ideas, easily use diverse testing techniques. </li></ul><ul><li>Quest tasks are rarely obvious, so the player should be quite creative and inventive to solve them and find the right way between many available. </li></ul>
  20. 20. Every problem usually has many possible solutions How can I get that bird?
  21. 21. Similarly – there are always plenty of test cases you might think of… 1 – try throwing something to hit it!
  22. 22. Similarly – there are always plenty of test cases you might think of… 2 – try getting the ladder …
  23. 23. Similarly – there are always plenty of test cases you might think of… 3 – use cable as a lasso …
  24. 24. Similarly – there are always plenty of test cases you might think of… 4 – get some bird food …
  25. 25. Similarly – there are always plenty of test cases you might think of… 5, 6, 7,… – your ideas?
  26. 26. Rich resources. <ul><li>Excellent exploratory testers build a deep inventory of tools, information sources, test data and friends to draw upon. </li></ul><ul><li>Query player might consider using external resources to get his mission completed: hints, walks through, other players advises. </li></ul>
  27. 27. Your testing won’t be effective if you’re not prepared well enough... I know nothing about botany…
  28. 28. Go get some spec. Talk to those who have information. Prepare some tools. spec tools
  29. 29. Finally, go GOOGLE it.
  30. 30. ET Basics Test Design Observation Critical thinking Diverse ideas Rich Resources Focus on the Mission
  31. 31. Scripted vs Exploratory <ul><li>Which is better? </li></ul>predictable repeatable easier to execute easier to report easier to measure time-taking preparation not very flexible flexible rapid may be very effective result-oriented harder to train harder to control
  32. 32. Scripted vs Exploratory <ul><li>Which is better? </li></ul>Depends on the context . … but as long as your task looks like Quest the best option is to become an explorer ;)
  33. 33. References <ul><li>What is Exploratory testing and how it differs from Scripted testing? (HTML) </li></ul><ul><li>Exploratory testing explained (PDF) </li></ul><ul><li>Exploratory testing dynamics (PDF) </li></ul>
  34. 34. p.s. <ul><li>I used screens from the brilliant Quest game called Machinarium . Find out more here: http://machinarium.net </li></ul>

×