Interactions Shapes Testing: Collaboration for Success
summary
16 years experience informs practical rules: testing’s job is to build confidence in product quality, not just find bugs; processes (define defect severity and exit criteria up front) matter before tools like Parasoft; a late high-severity defect was held to exit criteria, developers fixed it and the release still ships on time; consolidating reporting across 14 projects removes duplicated manual work (about 3–5 weeks saved per project), returning effort to testing and raising program-level confidence.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 3:03Software testing purpose
- 8:01Building testing confidence
- 12:15High-severity defects under pressure
- 17:38Stakeholder communication
- 23:18Consistent KPIs and reporting
- 28:18Question and answer session
related talks
36mHow programmers & testers can be productive
46mProject Culture and Team Responsibility for Quality
14mCommunication is Key: Lessons Learned from Testing in Healthcare Technology
24mThe more we test, the worse?
24mHello, assumption, my old friend! Or can a tester make a good product owner?
42mImproving Testing Quality by Changing Culture
36mHow to defuse a bomb Wait, I mean a bug
35mBetter, Faster, Stronger - Delivering High Quality Products