Capability
Repros — reproduction recipes
Capture the exact recipe that reproduces a defect — steps, payloads, URLs, environment — and reuse it across defects, test cases, and handovers.
How to use it
- 1 Open Repros in the side panel left rail.
- 2 Create a new repro from scratch, or click Save as repro from a failing step in the runner.
- 3 Add ordered steps, a payload block (JSON / XML / form data), and the environment that triggered it.
- 4 Attach screenshots, links, and short notes for context.
- 5 Link the repro to a defect or a test case — it appears in their detail panes and in exported reports.
Use cases
Intermittent defects
When a bug only repros with a specific payload or sequence, save it once so the next tester reproduces it on the first try.
Cross-environment validation
Reuse the same recipe in Dev, SIT, and UAT — the environment block makes the swap explicit.
Onboarding
New testers get a library of canonical repros for the team's edge cases on day one.
Vendor handoff
Export the repro as PDF / HTML so a third party can run it without access to your environment.
Tips
- Mark a repro as verified when it still works against the latest build — stale repros are surfaced for cleanup.
- Embed payloads with their content-type so they render correctly in exports.
- Repros support markdown in notes for code fences and tables.