“Three Paths to Better Developer Testing”
summary
Three practical moves: build whole team quality by shifting testing from one role to everyone; use pairing with a predictable script—ask “what have you tested?”, work the remaining scenarios together, then ask what are you still worried about—so developers move from “test this for me” to “help me test this”; and adopt coaching (books: Weinberg, Getting Naked, The Coaching Habit) to make testing reflective. The stated goal is to accelerate the achievement of shippable quality.
AI-written summary · about
related talks
36mWhole team quality: In the same boat or up the creek?
49mDeveloper + tester = quality++
46mDeveloper + Tester = Quality++
41mMartijn Goossens: Be a Better Test Friend to Your Team
46mProject Culture and Team Responsibility for Quality
59mBabble & Dabble: Creating Bonds Across Disciplines
48mTesting is Confidence - A Developer's Perspective
33mAgile Software Testing