Appendix A: What We´ve Learned Since Agile Testing
summary
Since the Agile Testing book the emphasis shifts to concrete practices: use a thousand-piece jigsaw as a reminder to prioritize feature-level acceptance tests over isolated story checks; automate business-facing specs so they become living documentation that must run green; treat test automation as code and pair testers with programmers or use a domain-specific language to keep GUI-driven ATDD viable; adapt the testing pyramid to context, manage technical debt, and practice via code retreats, testing dojos and remote pairing on two-week, ten-person teams.
AI-written summary · about
chapters (13)
- 0:00Intro
- 1:23Welcome
- 3:48Lisas Background
- 6:33Janets Background
- 7:52Feature Acceptance
- 16:00Sustainable Pace
- 17:50Test Automation
- 21:03The Pyramid
- 25:00Large Teams
- 30:24Distributed Teams
- 37:21Learning
- 45:42Stories
- 49:19Code Retreat
related talks
43mHow I fell in love with Agile testing and why you should, too!
08mTesting In Agile
33mAgile Software Testing
09m"A few things about Agile Testing"
24mEVERYTHING YOU MUST KNOW ABOUT AGILE TESTERS
43mAgile Testing Practices for Better Software Quality
39mMyths & Challenges of Agile Testing
01h 05mAdding value in an agile context