THE MAGIC NUMBER
summary
Claim: use the cumulative bug count slowdown as an exit criterion and stop when the curve flattens, tested on a website that went live with no major production bugs. Implementation uses a bug tracker and cumulative function, sometimes the derivative equals zero or bug density signals completion. Works best for small changes when testers are consistent; it needs comparison with historical data so compare with previous cycles and human judgment to catch regressions, environment issues, vacations, and scope differences.
AI-written summary · about
chapters (7)
- 0:00Start
- 1:35How much testing is enough?
- 1:58Constraints of resources
- 3:07What if you don't have a well-defined exit criteria?
- 7:33Usage
- 11:19Rule of thumb for functional web testing
- 13:02The Magic Number is...
related talks
50m#BugsZero
31mMeasure it or it didnt happen
47mHunting Heisenbugs
46mHow to Tame Bugs in Production: Successful Bug Managing Strategy in Five Steps
36mHow to defuse a bomb Wait, I mean a bug
29mYour Metrics Are Lying: How to Stop Reporting and Start Learning
10mBeyond “try harder”: Effective strategies to tackle bugs
44mTest Intelligence: Finding More Bugs in Less Time with AI