Problem reproduction means reliably triggering a failure under known conditions. Clarify the exact problem first: precise context makes the failure easier to reproduce, observe, analyze, and fix. section 10.3.2
Build enough context to identify the conditions that matter:
- Define the expected behavior and the observed behavior instead of accepting “It doesn’t work” as a complete diagnosis. section 10.3.2
- Record when the failure occurred, its environment, severity, user impact, and any available workaround. section 10.3.2
- Check application versions, devices or browsers, recent deployments, configuration changes, code merges, related incidents, and infrastructure problems. section 10.3.2
- Ask who reported the issue, where else it was reported, and who should receive updates. section 10.3.2
Turning a vague symptom into a reproducible problem
Replace “It doesn’t work” with a precise account of what should happen, what happens instead, when and where it happens, and which version or recent change may be involved. That clarification supplies the conditions needed for reliable reproduction. section 10.3.2
