Whole team quality: In the same boat or up the creek?
summary
Argues that testers remain essential but must evolve: testers learn code via an internal Java Protesters course (static-method focus) and pair with devs in mob testing sessions, write and review UI and unit tests together, and co-author automation. Teams move from six-week release cycles to continuous zero-day deploys in examples given. Concrete practices include role mapping, skill post‑it maps, enforced WIP limits, tester–developer code reviews, and pairing; these changes reduce handoffs and improve deploy frequency.
AI-written summary · about
chapters (6)
- 0:00Start
- 4:33What Would Buffy Do
- 8:22Teach Developers How To Test
- 10:24Mob Testing Sessions
- 12:25Avoid Testing Your Own Sinks
- 23:58Dynamic Persona and Context Based Team Composition
related talks
49mDeveloper + tester = quality++
08m“Three Paths to Better Developer Testing”
33mAgile Software Testing
59mBabble & Dabble: Creating Bonds Across Disciplines
46mDeveloper + Tester = Quality++
12mBeyond Testers: Embedding Test Expertise in Modern Software Development Teams
37mWe Are The Testers: You Will Be Assimilated
36mHow programmers & testers can be productive