| name | reproduce-a-bug |
| category | code |
| description | Build a minimal, repeatable reproduction of a software defect while controlling environment, inputs, and state. Use when a bug report is inconsistent, complex, or not yet proven outside the original system. |
reproduce-a-bug
Turn an anecdotal failure into an observable experiment. Reduce variables without erasing the condition that
causes the defect.
Inputs
- Gather the original report, affected version, environment, inputs, state, logs, and expected behavior.
- Identify destructive operations, production-only data, rate limits, and privacy or security constraints.
- Prepare a safe local, test, or isolated environment when possible.
Procedure
- Recreate the reported environment and record every intentional difference.
- Run the original steps once without modification and capture the result.
- Repeat enough times to estimate frequency without unsafe load.
- Control one variable at a time: version, configuration, data shape, timing, permission, network, or dependency.
- Reduce the steps, input, and code to the smallest case that still fails.
- Add a nearby control case that should pass and compare the observable difference.
- Restart from clean state to expose hidden cache, order, or shared-state dependence.
- Save commands, seed data, fixture, script, or test in a reproducible artifact.
- Record conditions that suppress the failure and any remaining nondeterminism.
- Hand off the minimal case with exact run instructions and expected output.
Boundaries
Do not copy sensitive production data, expose secrets, or run destructive experiments in a shared system.
Never call a defect fixed because it failed to reproduce once. Stop if reproduction can cause customer harm,
data loss, excessive cost, or a security incident.
