Testing != Quality
summary
Claim: testing is an information provider, not the same as quality. Argues quality = value to people who matter, so teams must cover discovery, delivery and ops not just correctness. Proposes a quality coach model with a hub-and-spoke enabling team that produces test automation frameworks pushed into repos, runs short missions (≈three months) to upskill squads, and leans on monitoring, alerting, OpenTelemetry and distributed tracing to close feedback loops. Story splitting and better feedback reduce environment and release risk.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:04Testing vs. quality
- 2:49Defining quality and value
- 6:29Product quality degradation
- 10:06Expanding the scope of quality
- 14:02Threats to quality
- 17:42Quality coaching models
- 21:18Implementing a coaching role
- 25:33Facilitating team quality
- 30:08Beyond testing metrics
related talks
34mAre we Quality Assurance or Testers?
31mQuality Engineering mindset and TBS
50mThe End of Testing as We Know It
51mQuality Assurance vs. Testing
34mesting in modern times: A story about quality and value
36mWhole team quality: In the same boat or up the creek?
28mQuality as an attitude – From Testing to Quality Engineering to…what?
46mProject Culture and Team Responsibility for Quality