SLASSCOM: Breaking illusions with Testing
•
0 likes•150 views
The document discusses exploratory testing and lessons learned. It advocates for being intentional about learning, embracing serendipity through play, and pushing constraints to find workarounds. Testers should focus on understanding over just using a system, and help improve testability for developers. Automating tests can document edge cases. While scores may not reflect quality, what engages users? Overall it promotes skills like deliberate discovery and practicing to get luckier at exposing assumptions.
Recommended
More Related Content
What's hot
What's hot (20)
Similar to SLASSCOM: Breaking illusions with Testing
Similar to SLASSCOM: Breaking illusions with Testing (16)
More from Maaret Pyhäjärvi
More from Maaret Pyhäjärvi (12)
Recently uploaded
Recently uploaded (20)
SLASSCOM: Breaking illusions with Testing
- 1. @maaretp http://maaretp.com with Testing by Maaret Pyhäjärvi
- 5. @maaretp http://maaretp.com http://visible-quality.blogspot.fi/2017/03/from-appreciation-of-shallow-testing.html She's like "I want to exploratory test your ApprovalTests" and I'm like "Yeah, go for it", cause it's all written test first and its code I'm very proud of. And she destroyed it in like an hour and a half.
- 6. @maaretp http://maaretp.com Testers don’t break the code, they break your illusions about the code. - Adapted from James Bach
- 8. @maaretp http://maaretp.com Testers don’t break the code, they break your illusions about the code. - Adapted from James Bach WHATEVER NECESSARY
- 9. @maaretp http://maaretp.com Code doing what it’s supposed to. Product doing what it would need to. Product doing only what it is supposed to do. Basic Illusions: Code Making a Product Other Illusions: Ideas Leading to Code Process being able to deliver with a change in mind People having skills to deliver well. Business model driving the selection of right focus.
- 10. @maaretp http://maaretp.com Pair and Ensemble Remotely Results-oriented ExploratoryTesting Working without a Product Owner
- 11. @maaretp http://maaretp.com Pair and Ensemble Remotely Results-oriented ExploratoryTesting Working without a Product Owner
- 12. @maaretp http://maaretp.com Ensemble Testing Strong Style Traditional I have an idea… Please take the keyboard I have an idea… Give me the keyboard
- 13. @maaretp http://maaretp.com Accidental Learning by being Intentional about Learning
- 14. @maaretp http://maaretp.com Pair and Ensemble Remotely Results-oriented ExploratoryTesting Working without a Product Owner
- 15. @maaretp http://maaretp.com (Exploratory) Tester Product is my external imagination
- 16. @maaretp http://maaretp.com Never be bored. Heuristics
- 17. @maaretp http://maaretp.com In the beginning, you know the least. Heuristics
- 18. @maaretp http://maaretp.com Poke it until it pops Variable recognition and persistency heuristics from Alexandra Schladebeck Heuristics
- 22. @maaretp http://maaretp.com Test Automation is Documentation!
- 23. @maaretp http://maaretp.com Pair and Ensemble Remotely Results-oriented ExploratoryTesting Working without a Product Owner
- 25. @maaretp http://maaretp.com Continuous Delivery No Jira No Estimates No Product Owner No Projects No Scrum
- 26. @maaretp http://maaretp.com “Best Team in Corporate R&D”
- 27. @maaretp http://maaretp.com Learning Superpower and core of exploring
- 28. @maaretp http://maaretp.com Testers don’t break the code, they break your illusions about the code. - Adapted from James Bach WHATEVER NECESSARY
- 29. @maaretp http://maaretp.com vs. LinearViewpoint I know everything you do! You have nothing left to teach me Reality I know more than you do! There is still so much more I can learn from you Learning
- 30. @maaretp http://maaretp.com Things Can Look Different from Different Perspectives
- 33. @maaretp http://maaretp.com Lesson 1. Testing is not using the system.You need to be more driven to information and understanding. More intentional.
- 34. @maaretp http://maaretp.com Lesson 2. Intent is not enough. Serendipity happens through elements of play and making unplanned connections.Awareness of what you know and how you know it becomes essential.
- 35. @maaretp http://maaretp.com Lesson 3.You are in control. When system gives you a hard constraint, there are still ways you can work through that constraint. If you can simplify or isolate, do that. Complex can happen later.
- 36. @maaretp http://maaretp.com Lesson 4.Testability.When something is hard to do, remember there’s a developer somewhere who needs to share the pain to build smarter next time.
- 37. @maaretp http://maaretp.com Lesson 5.You got tools. Find them.You pull in what you need, not rely on just what you’re given.
- 38. @maaretp http://maaretp.com Lesson 6.Yes, that automation of permutations integrated with vocabulary would come in handy. What you can’t find but want, you can build.
- 39. @maaretp http://maaretp.com Lesson 7. It really does not calculate scores right. But does that matter - what is quality for this game?What creates emotions relevant enough to impact user’s behavior?
- 41. @maaretp http://maaretp.com The more I practice, the luckier I get – Arnold Palmer
- 42. @maaretp http://maaretp.com It’s not that I’m so smart, I just stay with the problems longer. – Albert Einstein See also: http://blogs.scientificamerican.com/guest-blog/the-forgotten-life-of-einsteins-first-wife/
- 43. @maaretp http://maaretp.com Deliberate Discovery Skills 1 2 4 5 3 1 2 4 5 : Phrase and illustration by Liz Keogh @lunivore
- 44. @maaretp http://maaretp.com 2020 2016 MIATPP Most Influential Agile Testing Professional Person #PayToSpeak #TechVoices #EnsembleTesting #EnsembleProgramming #StrongStylePairing #ExploratoryTesting #TestAutomation #ModernAgile #AwesomeTesters Maaret Pyhäjärvi (from Finland) Email: maaret@iki.fi Twitter: @maaretp Web: maaretp.com Blog: visible-quality.blogspot.fi (please connect with me through Twitter or LinkedIn)