An escaped bug, sometimes called an escaped defect or production bug, is a bug that gets past testing and is found in production, often by users. Some are obvious in hindsight, such as a typo on a home page.
Why it matters: No testing finds every bug, so escaped bugs will happen. How a team responds decides whether it learns from them or just looks for someone to blame.
In practice: Teams review escaped bugs to understand why they slipped through, without blame. Testers adjust their heuristics, test ideas and assumptions, and many name their heuristics so they can recall them next time.
Examples:
- A typo in a large heading that nobody noticed until the site went live.
- A team reviewing escaped bugs each month to adjust its heuristics and test ideas.
Common pitfalls:
- Asking “who tested this?” instead of “what can we learn?”
- Expecting testing to catch everything and treating every escape as a failure.
How do you reduce escaped bugs? Create many test ideas, think about what-ifs, use fresh eyes, pair with others, challenge “no one would do that” and act on gut feelings by looking for evidence.
