Next step · What to do next

Add automatic tests for the important flows

What you may see

I am afraid every change will break something

Why this step

A few tests on the flows that make money (order, payment, booking, sign-in) catch most breakage before customers do.

Before you start

List the 5 flows that must never break.

The prompt for this step

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.

Any error or warning you see now

What you have now (tool, framework, where it is hosted)

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

Prompt language

You are a senior engineer and careful product advisor who builds small business websites and apps, and explains every step 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.

WHAT I WANT NEXT
Add automatic tests for the important flows

ANY ERROR OR WARNING I SEE NOW (write "none" if there is none)
[paste the exact error here]

WHAT I HAVE NOW (the tool I used, the framework, where it is hosted)
[write in a few words what you did before it happened]

WHY THIS STEP
A few tests on the flows that make money (order, payment, booking, sign-in) catch most breakage before customers do.

DO THESE STEPS, IN THIS ORDER
1. Choose a light test setup that fits the framework (unit tests for the logic like money and dates, and a few browser tests for the main flows) and explain it in four lines.
2. Write tests for the money and date logic first (edge cases, three-decimal amounts, midnight in Kuwait time), then the main flows on a phone-size window in English and Arabic.
3. Use test data only, never real customers or live keys; add one command to run all tests.
4. Show a test failing on purpose once, so I trust that it can fail.
Stop and tell me if what you see does not match a step. Do not skip ahead.

CHECK THAT IT WORKED
- One command runs all tests and they pass; a deliberate bug makes one fail.
Tell me exactly what I should see on the screen when it works.

DO NOT CHANGE
- Do not edit tests to make them pass.
- 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

Choose a light test setup that fits the framework (unit tests for the logic like money and dates, and a few browser tests for the main flows) and explain it in four lines.
Write tests for the money and date logic first (edge cases, three-decimal amounts, midnight in Kuwait time), then the main flows on a phone-size window in English and Arabic.
Use test data only, never real customers or live keys; add one command to run all tests.
Show a test failing on purpose once, so I trust that it can fail.

Do not do this

Do not test with live payment keys.
Do not edit tests to make them pass.

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

Try another entry