Developer + tester = quality++
summary
Explains how Agile shifts responsibility for testing to the whole team and promotes close collaboration between developers and testers to improve product quality. Describes motivations for paired developer–tester work, concrete practices and approaches at different stages from requirements to customer acceptance, and the benefits each side gains from this collaboration.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 3:40Testers matter
- 5:04Dev-tester conflicts
- 8:55Built-in quality
- 10:39Planning for quality
- 15:32Test case reviews
- 21:06Design for testability
- 25:38Interim demos
- 30:07Pair testing benefits
- 34:02Client pair demos
- 37:33Team communication
- 40:21Conclusion
- 41:23Q&A: Need testers?
- 43:11Q&A: Silent devs/testers
- 44:16Q&A: Adopting practices
- 46:42Q&A: Local pair testing
related talks
46mDeveloper + Tester = Quality++
36mWhole team quality: In the same boat or up the creek?
08m“Three Paths to Better Developer Testing”
43mAgile Testing Practices for Better Software Quality
33mAgile Software Testing
21mImproving Quality Through Effective Communication Between Tester and Developer
01h 05mAdding value in an agile context
30mCollaboration Between the Dev and the Test Team