What are repro steps? Definition and how to write them

Repro steps — short for reproduction steps — are the minimal ordered sequence of actions that reproduces a defect on demand.

They are the section of a bug report that turns "I saw this once" into "anyone can see it." Without them, the engineer's first job is to recreate the conditions; with them, the first job is the fix.

What makes a good list

Start from a known state — "logged in as a new trial user on staging" — so the reader does not have to guess prerequisites. Then list the actions in order, one per line, each specific enough to follow without interpretation. Stop at the moment the defect appears.

The implicit contract is that following the steps lands the reader in the broken state. If a step is wrong or out of order the contract breaks and the engineer goes back to investigation work the reporter already did. For intermittent bugs, document the conditions and frequency instead of pretending a deterministic sequence exists.

For AI-agent-driven fixes the steps double as a verification script. The agent can re-run them after applying a fix and confirm the broken state no longer appears.

Frequently asked questions

How detailed should repro steps be?

Detailed enough that a person who has never seen the bug can follow them and land on the same broken state. Skip the obvious ("open a browser"); include the not-obvious ("apply coupon WINTER, then change quantity to 2").

What if the bug is intermittent?

Document the conditions under which it has reproduced, the frequency, and any state that seemed to influence it. "Three out of five attempts after a fresh login" is more useful than "sometimes."