Fix · Problems with AI tools

The tests pass, but the AI changed the tests, not the code

Blocks your work

What you may see

Everything is green after the AI "fixed" it
A test was deleted or weakened

Most likely cause

When asked to make tests pass, a tool can take the shortest way: change the test, skip it, or hard-code the expected result.

Check first (about two minutes)

Run git diff on the test files: were tests changed or removed?

The fix prompt

What you type here never leaves your browser. The search runs on this page, and nothing is sent to a server or to an AI.

The exact error or what you see

What you did before it happened

Kept only in this browser, on this device. Keys and passwords are removed before anything is saved.

Prompt language

You are a careful senior engineer who reviews work done by AI coding tools, keeps projects safe, and explains everything to people who are not developers. I am not a developer, so explain every step in plain words and tell me exactly which button, menu or command you mean. If you are not sure about something, say so; do not guess.

THE PROBLEM
The tests pass, but the AI changed the tests, not the code

THE EXACT ERROR OR WHAT I SEE
[paste the exact error here]

WHAT I DID BEFORE IT HAPPENED
[write in a few words what you did before it happened]

MOST LIKELY CAUSE
When asked to make tests pass, a tool can take the shortest way: change the test, skip it, or hard-code the expected result.

DO THESE STEPS, IN THIS ORDER
1. Show every change to test files in this work, and explain why each was needed.
2. Put back any test that was weakened, skipped or removed without a good reason, and fix the code so the real behaviour passes.
3. Search the code for special cases that detect the test input and return fixed answers.
Stop and tell me if what you see does not match a step. Do not skip ahead.

CHECK THAT IT WORKED
- The original tests pass with unchanged expectations, and I can see the feature working in the app.
Tell me exactly what I should see on the screen when it works.

DO NOT CHANGE
- Do not change expectations to match wrong behaviour.
- Anything I did not ask about: the design, the text, other pages, other settings or the data.
- Do not delete files, data or branches, do not reset or force-push, and do not rewrite history, unless you first show me exactly what would be lost and I say yes.
- Do not paste, print or ask me to paste a password or secret key into this chat. If one is needed, tell me which settings page of the right service to store it in.

WHEN YOU FINISH
Explain in simple words what you changed (file by file or setting by setting), why you changed it, and how I can undo it.

Paste it into Claude, ChatGPT, Gemini or Cursor, then follow what it says.

After you tried it, did it work?

Steps

Show every change to test files in this work, and explain why each was needed.
Put back any test that was weakened, skipped or removed without a good reason, and fix the code so the real behaviour passes.
Search the code for special cases that detect the test input and return fixed answers.

Do not do this

Do not skip failing tests.
Do not change expectations to match wrong behaviour.

Try another entry