Prove that it works

For this step

Do exactly what your user would do, start to finish, without touching the code.

• Use the main action from your brief.
• Click every button and link once.
• For a browser-local tool: add, edit, delete, save, then refresh the page.

A good-looking page is not evidence that its action works. Click the thing your user would click.

For this step

In Chrome or Edge press F12 to open developer tools, then Ctrl+Shift+M (Mac Cmd+Shift+M) to switch on the device toolbar and pick a phone. If that feels fiddly, just drag the browser window until it is narrower than your hand.

If something breaks, ask the coach for the smallest fix to that one control. Do not redesign the page.

For this step

Compare what you have against project-brief.md and design.md. Fix anything that blocks the main action, then record the check in build-status.md: what you tested, at which width, and what passed.

All three count. Keep new feature ideas for the next build. This step closes what you promised, it does not extend it.

Before you move on

Common mistakes

• Testing by reading the code instead of using the page.
• Skipping the refresh test on a tool that saves data.
• Calling a desktop-only page finished.
• Fixing a broken layout by asking for a redesign.
• Adding one more feature instead of recording the proof.