Reproduction Steps
// Definition
A numbered sequence of actions a developer can follow to reliably trigger a defect from a known starting state. High-quality reproduction steps include: the environment and version, preconditions and test data, each action in order, and the actual vs expected result. Reproducibility is the single biggest factor in defect resolution speed — a bug that cannot be reproduced is rarely fixed. For intermittent defects, include the reproduction rate and any environmental conditions that affect it.
// Related terms
Defect
A flaw in a software system that causes it to behave in an unintended or incorrect way — also called a bug or fault. A defect arises when actual behaviour diverges from expected behaviour defined by requirements or specification. In QA workflow, a defect is formally logged with reproduction steps, severity, and priority, then tracked through the bug lifecycle from discovery to verified closure. The distinction that matters in practice: an error is the human mistake, a fault is the resulting code flaw, and a failure is the observable incorrect behaviour at runtime.
Bug Lifecycle
The stages a defect passes through from discovery to closure: New → Assigned → In Progress → Fixed → Verified → Closed (with possible Reopened, Deferred, or Rejected branches).
Exploratory Testing
Simultaneous learning, test design, and execution — the tester explores the app, forms hypotheses, and probes them, with no pre-scripted steps. Most effective when time-boxed and chartered.