Spielerando

My AI says the bug is fixed, but did it fix it or only stop the checks from running

Fewer red marks after a fix can mean the problem is gone, or that a check disappeared, or that a new problem replaced the old one. This entry shows your AI how to sort the before and after results into fixed, still broken, newly broken and never run.

Why this works

A fix is proven only if the check that failed ran again and now passes. Counts can hide a swap, and a deleted or renamed check makes red marks vanish without anything improving, so compare the names, not the totals.

When not to use it

It cannot help when you have no checks at all, or when they are so thin that passing proves little. Write a check that shows the bug first, watch it fail, then fix.

In the full entry

  • What to build, step by step
  • Starting values and the reason for each
  • 3 common mistakes and the fix
  • 28 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 "My AI says the bug is fixed, but did it fix it or only stop the checks from running" (read_entry did-the-ai-fix-or-just-hide-it) 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