Transparency - A holistic approach to software quality
summary
Argues that shifting from “testing” to transparency yields measurable gains: builds a deprioritizer bot that prunes stale bugs, creates simpler test-automation wrappers, and fixes a misleading status graph so teams stop wasting hours. Measures a shared test environment as costing 16 hours/week and converts that to dollars to win funding, and plants a “do not test in production” trap that generates three emails a week revealing why people hit production. Outcomes: cleaner backlog, faster releases (months→weeks), fewer risky production tests.
AI-written summary · about
chapters (4)
related talks
34mesting in modern times: A story about quality and value
15mHow to NOT waste time
06mLightning Talk: Automated Testing Done Right
15mTransforming Testing: The Power of TestOps
50mThe End of Testing as We Know It
42mImproving Testing Quality by Changing Culture
24mTesting Less, Achieving More: How we mastered The Art of Strategic Testing
10mThe value of testing