AgileTD Scandia: Mob Testing
0 likes396 views
The document discusses lessons learned from a year of mob testing. Mob testing involves testing as part of a mob programming team, where all team members work at the same time on the same computer. Key aspects of mob testing discussed include strong-style navigation where all ideas must go through others' hands, the importance of kindness and respect, and exploring testing ideas in a varied learning experience. Mob testing is said to build habits and transfer skills over time better than just passing on knowledge. The document advocates mobbing on any testing activity and notes how testing provides various benefits at different stages of development.
AgileTD Scandia: Mob Testing
- 1. @maaretp http://maaretp.com Mob Testing Lessons from aYear of #MobTesting by Maaret Pyhäjärvi
- 2. @maaretp http://maaretp.com So, What is Mob Testing (and Programming) Let’s Define the Basics
- 3. @maaretp http://maaretp.com "All the brilliant people working on the same thing, at the same time, in the same space, on the same computer." -- Woody Zuill
- 4. @maaretp http://maaretp.com Mob Testing is Mob Programming so that: • You’re a tester in a mob programming team OR • Activity you mob on is testing
- 5. @maaretp http://maaretp.com Mobbing Setup and Roles Driver Navigators Designated Navigator Facilitator
- 6. @maaretp http://maaretp.com Strong-Style Navigation “For an idea to go from your head to the computer it must go through someone else’s hands” *http://llewellynfalco.blogspot.fi/2014/06/llewellyns-strong-style-pairing.html
- 9. @maaretp http://maaretp.com Observations Retrospective ONE IDEA PER STICKY NOTE CAPITAL LETTERS EASY TO READ FEW WORDS Lowercase letters Don’t write in cursive or in biro Avoid writing too much on one single note as it takes a while for people to read the whole thing! • IDEA 1 • IDEA 2 • IDEA 3 ≠ ≠ ≠ ≠
- 10. @maaretp http://maaretp.com My Mob Testing Experience Working and Teaching in a Mob
- 11. @maaretp http://maaretp.com A Non-Programmer Meets Mob Programming
- 12. @maaretp http://maaretp.com An All-Female Hackathon
- 13. @maaretp http://maaretp.com Teaching Exploratory Testing in a Mob
- 14. @maaretp http://maaretp.com Cognitive Dissonance
- 16. @maaretp http://maaretp.com Stealth Exploration
- 17. @maaretp http://maaretp.com My Developers Get Exploratory Testing!
- 18. @maaretp http://maaretp.com Progress with Team Test Automation
- 19. @maaretp http://maaretp.com Exploring in a Mob Creating a varied learning experience
- 20. @maaretp http://maaretp.com Testers acquire a lot of implicit knowledge
- 22. @maaretp http://maaretp.com Vocalizing your ideas
- 24. @maaretp http://maaretp.com Mapping Coverage, Bugs and Questions
- 25. @maaretp http://maaretp.com Building habits and transferring skills over passing knowledge
- 26. @maaretp http://maaretp.com What Testing gives Us UnitTesting ExploratoryTesting SPEC FEEDBACK REGRESSION GRANULARITY GUIDANCE UNDERSTANDING MODELS SERENDIPITYTesting as artifact creation Testing as performance
- 27. @maaretp http://maaretp.com Before implementing While implementing Before production While in production Testing as artifact creation Testing as performance (exploration) Ways to think of testing peak at different moments with regards to adding a capability TOTALS Mob on Any Testing Activity!
- 28. @maaretp http://maaretp.com Product is my external imagination I am my developer’s external imagination
- 29. @maaretp http://maaretp.com The Usual Concerns Wouldn’t we get more done individually?
- 32. @maaretp http://maaretp.com Best ideas win when you care about work over credit
- 33. @maaretp http://maaretp.com From technical debt to technical assets
- 34. @maaretp http://maaretp.com Best face forward in a group
- 36. @maaretp http://maaretp.com You have great ideas even if you did not know how to turn them to code – removing the distance is worth the struggle.
- 38. @maaretp http://maaretp.com Maaret Pyhäjärvi Email: [email protected] Twitter: @maaretp Web: maaretp.com Blog: visible-quality.blogspot.fi (please connect with me through Twitter or LinkedIn)