A rare bug did not show up in ten test runs: is it fixed?

A bug that appears only now and then can easily hide through a handful of clean tries after a fix. This entry shows how many clean runs you need before you may say it is gone, and what a run of clean tries can and cannot tell you about how often it still happens.

Why this works

Each clean try only slightly lowers the chance that the bug is still there, because a rare bug often misses by luck. How many tries you need depends on how rare it was, and the answer is a limit on how often it could remain, not a promise.

When not to use it

It breaks down when you do not know how often the bug showed before, or when each try repeats the same start, so the tries are not independent. Then make the bug appear on purpose, or get the logged rate first.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 4 common mistakes and the fix
• 15 lines of example code with 3 checks that pass
• How your AI shows you that it works

Say this to your AI

Use the Spielerando entry "A rare bug did not show up in ten test runs: is it fixed?" (read_entry how-many-clean-test-runs-before-a-rare-bug-is-gone) in my game. Build it step by step, and show me how you checked that it works.

Or skip this and connect the MCP: your AI then finds all of this by itself.Connect the MCP