Test, fix, and try again

A bug is a clue

A bug is a mistake in how a program works. Write what you did, what you expected, and what happened. Copy the useful error text, but remove keys and private data.

Preview errors can come from missing files, packages, settings, or a failed start command. Open diagnostics. Fix the cause. A screenshot alone may not tell the whole story.

Check more than the happy path

Try a blank form, a long title, a phone screen, and keyboard use. Does the text stay visible? Does the page tell you when a request fails? Does a button do the action it claims?

Use a small test for a bug that could come back. Test important money, access, and data rules more carefully. Sample data can help with layout, but it does not prove the real service works.

Try these steps

1. Record exact steps to reach the bug.
2. Read diagnostics and ask for a narrow fix.
3. Repeat the steps, then test one nearby case.

A real-world example

A form with no email should show a clear message. A failed request should not say “Sent.” A preview with sample records must not be treated as a live database check.

Ask AI for help

Copy this prompt into the tool you use. Fill in the blanks. Check what it gives you.

Expected: ___. Actual: ___. Steps: ___. Error: ___. Find the cause and propose the smallest safe fix. Tell me how to check it.