How I fell in love with Agile testing and why you should, too!
summary
Argues that agile testing shifts focus to defect prevention over detection, with testers pairing with developers and customers for daily backlog reprioritization and shared acceptance criteria; recommends a mixed toolbox rather than one vendor solution, uses design sprints and impact mapping, and runs recurring mid-sprint show-me sessions for immediate feedback. Notes avoiding fragile UI mobile automation in favor of crowdtesting on devices, rotates a team member through customer support weekly, and treats testing as continuous across the DevOps pipeline.
AI-written summary · about
chapters (14)
- 0:00Introduction and speaker intro
- 0:52Agile testing from bottom up
- 3:12Personal journey into Agile testing
- 7:14Why I fell in love with testing
- 11:55Agile testing principles
- 15:34The power of three amigos
- 19:30Types of testing and quadrants
- 23:08Test automation toolbox
- 27:08DevOps and continuous testing
- 29:01Test lead challenges and solutions
- 35:57Including customer support
- 38:25Techniques beyond testing
- 40:36Evolving beyond testing roles
- 42:03Call to action and learning
related talks
08mTesting In Agile
33mAgile Software Testing
09m"A few things about Agile Testing"
58mAppendix A: What We´ve Learned Since Agile Testing
39mMyths & Challenges of Agile Testing
43mAgile Testing Practices for Better Software Quality
34mHelping Testers Add Value to Agile Projects
01h 22mAgile - The Road Towards Organizational Agility - Progress & Challenges Examined