Writing a report someone can act on.

1.What a mission is

One project, one thing to test, and a test case to work through. The builder has written an ordered list of steps: each one is an action to take and what they believe should happen when you take it.

Your job is to do each step and say whether it did that. You are not being asked to review the product, guess at causes, or be kind.

2.Read the whole test case first

Before you open anything, read every step. You will spot a flow that needs an account, or a step that depends on the one before it, and you can plan around both.

Then open the project in another tab and keep the mission page beside it. The log is meant to be filled as you go, not reconstructed from memory at the end — that is where “it broke somewhere around checkout” comes from.

3.Pass, fail, or blocked

Every step gets one of three answers, and the third one is the one people get wrong.

Pass

It did what the builder said it would.

Fail

It ran, and did something else.

Blocked

You could not get to this step at all.

Blocked is not a softer fail. Fail means the step ran and did the wrong thing. Blocked means you never got to it — the previous step broke, the page would not load, the feature needs an account you could not create. Marking a blocked step as a fail reports a bug in a feature nobody reached, and the builder will go looking for it.

Blocked is often the most urgent thing in your report, because everything after it went untested. Do not feel you are giving up by using it.

4.What each field wants

A passing step asks nothing else of you.Mark it and move on — what it confirms is the builder's own expected result, which is already recorded on the row. You are never asked to restate it.

A failed step and a blocked step both ask for the same three things. All three are required on both — the form will not let you submit until they are filled, and each is capped at 500 characters.

What actually happened

What you saw, in the order you saw it. Not what you think caused it — a guess about the cause is the one thing the builder can check for themselves and you cannot.

Summary of the issue

One line. This is what the builder reads in a list of twenty rows, so it has to survive on its own: “Checkout button does nothing on mobile Safari”, not “doesn't work”.

Steps to reproduce

Numbered, starting from somewhere the builder can start — a URL or a logged-out browser. If you cannot reproduce it a second time, say so; that is useful too.

Yes, a blocked step asks for all three. Something stopped you, and what stopped you is the entire content of that row.

5.Screenshots

At least one screenshot is required on every report, and you can attach up to 10. PNG, JPG or WEBP, under 5 MB each — the form compresses them before upload, so a full-resolution phone screenshot is fine.

Shoot the problem, not the homepage

• Capture the broken state while it is on screen. A screenshot taken after you reloaded shows a working page.
• Include enough around the problem to place it — the URL bar, the page heading.
• An error message is worth a screenshot even if you also typed it out. Exact text matters.

6.Anything else

There is one free-text box at the end of the report. It is optional, and it is for the things that did not belong to any single step: the flow felt long, the copy confused you, something you noticed on the way past.

Do not put a step's issue in here. A problem filed against its step is one the builder can act on; the same problem in the comment box has lost the thing it was about.

7.What gets rated well

The builder reviews every report and rates it out of five. Ratings are the whole of your standing here — there is no payment, and nothing else accumulates.

• Specific. One clear problem per row, with what you saw.
• Reproducible. Someone else can follow your steps and land on the same screen.
• Shown. A screenshot of the actual failure.
• Honest about the gaps. Say what you could not reach and why. A report that marks three steps blocked and explains them is far more useful than one that guesses.

A report that finds nothing wrong is a real result. Pass every step, attach your screenshot, and say so in the comment.