An irreproducible bug, also called an unreproducible or non-reproducible bug, is a bug that cannot be reproduced consistently, even after several attempts. It may appear once and then vanish, or show up only under conditions nobody has yet identified, which makes it hard to track down and fix.
Why it matters: These bugs are easy to dismiss because nobody can show them on demand, and developers may push back with "it does not happen on my machine" or a lack of time. Yet they are often warning signs of deeper problems, such as operating system differences, third-party library mismatches or user-specific configuration, that can cause bigger failures later.
In practice: Testers report irreproducible bugs anyway, but with extra care. A useful report:
- Labels the issue clearly as irreproducible.
- Describes the failure precisely, with screen recordings, console logs and API calls.
- Lists variables that might matter, such as browser, OS version, library version and hardware.
- Explains which reproduction attempts have already been tried.
Follow-up work helps too: varying data, settings and the timing of interactions, preserving the test machine's state, and checking the bug tracker for similar past failures.
Examples:
- A crash seen once during exploratory testing is captured from a screen recording that was already running.
- A failure that appears only on one tester's laptop turns out to depend on an unusual Java runtime version.
- An error appears only when steps are clicked through very quickly, revealing a timing problem.
Common pitfalls:
- Closing the report as "cannot reproduce" without a resolution code or tag, so the same issue cannot be linked when it returns.
- Reporting the moment the bug appears without first preserving the system state or trying variations.
Is an irreproducible bug the same as an intermittent bug? They overlap. An intermittent bug comes and goes under the same conditions, while an irreproducible bug is any bug the team has not yet managed to make happen again on demand.
Should you report a bug you cannot reproduce? Yes. A careful report with evidence and context is often the first step towards finding the cause.
