A scare bug shows up one time in twenty and I cannot tell when it is really fixed

Five good runs in a row after a fix feel convincing, yet for a rare bug they prove very little. This entry works out how many clean runs you need for a given chance of the bug and how sure you can be afterwards.

Why this works

A rare problem hides most of the time, so a few good runs say little: they happen by luck again and again. Only when luck would have to be very unlikely does a clean streak start to mean the problem is gone.

When not to use it

It is the wrong tool when you can see the cause in the code or reproduce the bug on demand: fix it and test that exact case once. It also fails if the bug only appears under conditions your reruns never create.

In the full entry

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

Say this to your AI

Use the Spielerando entry "A scare bug shows up one time in twenty and I cannot tell when it is really fixed" (read_entry how-often-to-rerun-a-rare-scare-bug) 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