Download to read offline
Uploaded byMaaret Pyhäjärvi
AGRS2019: Breaking illusions with Testing
The document discusses how testers break illusions about code by finding issues and areas for improvement. It provides examples of common illusions such as code working as intended, the product meeting requirements, and the development process supporting changes. The document advocates an exploratory testing approach using heuristics to generate new test ideas and pushing software to its limits. It also emphasizes the value of learning from testing and having a mindset of continuous improvement.
More Related Content
Similar to AGRS2019: Breaking illusions with Testing
AGRS2019: Breaking illusions with Testing
- 1. @maaretp http://maaretp.com Breaking Illusions withTesting by Maaret Pyhäjärvi
- 2.
- 3.
- 4. @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.
- 5. @maaretp http://maaretp.com Testers don’tbreak the code, they break your illusions about the code. - Adapted from James Bach
- 6.
- 7. @maaretp http://maaretp.com Code doingwhat 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.
- 8.
- 9. @maaretp http://maaretp.com (Exploratory) Tester Product ismy external imagination
- 10. @maaretp http://maaretp.com Never bebored. Heuristics
- 11. @maaretp http://maaretp.com In thebeginning, you know the least. Heuristics
- 12. @maaretp http://maaretp.com Poke ituntil it pops Variable recognition and persistency heuristics from Alexandra Schladebeck Heuristics
- 13.
- 14. @maaretp http://maaretp.com Structure Function Data Platform Operations Time Idea generationheuristics from James Bach / Michael Bolton, Rapid SoftwareTesting
- 15. @maaretp http://maaretp.com Approvers do • Formatting • Sorting • File Extensions • Scrubbing (removing common inconsistencies) • Serialization(saving to a file) • Mocking • Proxying • Rendering • Execution (e.g. retrieve the URL) • Aggregating test cases • File naming • PRINCIPLE: ”Every time you handle this type of object, you do these things to it.” I LEARNED ABOUT FUNCTIONS
- 16. @maaretp http://maaretp.com Reporters do • Waiting • Scrubbing (removing common inconsistencies) • Execution • Launching • Serialization • Decompilation • Chain of responsibility • Creating Approved file • Environmental awareness I LEARNED ABOUT FUNCTIONS
- 17. @maaretp http://maaretp.comI LEARNEDABOUTTHE ENVIRONMENT
- 18.
- 19. @maaretp http://maaretp.com Code doingwhat it’s supposed to. Product doing what it would need to. Product doing only what it is supposed to do.
- 20. @maaretp http://maaretp.com Three OtherIllusions The Ideas Leading into Code
- 21. @maaretp http://maaretp.com Illusion typeVI: Businessmodel driving the selection of right focus.
- 22. @maaretp http://maaretp.com Insight andillustration from Allan Kelly, @allankellynet
- 23. @maaretp http://maaretp.com Illusion typeV: Peoplehaving skills to deliver well.
- 24.
- 25. @maaretp http://maaretp.com Illusion typeIV: Process being able to deliver with change in mind.
- 26.
- 27. @maaretp http://maaretp.com Continuous Delivery NoJira No Estimates No Product Owner No Projects No Scrum
- 28. @maaretp http://maaretp.com Learning Superpower andcore of exploring
- 29. @maaretp http://maaretp.com vs. LinearViewpoint I know everything youdo! 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 CanLook Different from Different Perspectives
- 31.
- 32.
- 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.Youare 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 somethingis 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.Yougot 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?
- 40.
- 41. @maaretp http://maaretp.com The moreI practice, the luckier I get – Arnold Palmer
- 42. @maaretp http://maaretp.com It’s notthat 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 Maaret Pyhäjärvi Email:maaret@iki.fi Twitter: @maaretp Web: maaretp.com Blog: visible-quality.blogspot.fi (please connect with me through Twitter or LinkedIn)