Beyond “Just Try Harder”- Three effective strategies to tackle bugs
summary
Shows how a health‑tech platform cuts bugs by changing the system not people: shrinks a 30‑minute test suite into one minute local / five minute pipeline targets by tagging and moving tests down (unit/integration/e2e), caches and parallelizes CI, uses Docker for integration DBs and Sonar for static analysis, dark‑launches with LaunchDarkly and contract JSONs, maps events with unique IDs, and moves releases from biweekly to every two days, saving roughly 20 hours per developer per month.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 4:10Bugs slip through costs
- 11:58Test runtime prioritization
- 18:29Strangler fig refactoring
- 23:46Small changes merge often
- 30:50Feature flags rollouts
- 33:21Firefighting to feedback
- 34:27Q&A
related talks
10mBeyond “try harder”: Effective strategies to tackle bugs
44mTest Intelligence: Finding More Bugs in Less Time with AI
36mHow to defuse a bomb Wait, I mean a bug
14mCommunication is Key: Lessons Learned from Testing in Healthcare Technology
16mShift Left, Not Off a Cliff: Why Your Testing Strategy Is Breaking Developers
53mTransforming testing methodologies: From manual to robust strategies
50mTest Intelligence for Architects
58mTesting Strategy - New Model, Better Outcomes