How to apply this guide
Record how to reproduce a product issue and keep predicted outcomes separate from observed results.
Start with
Say the starting state, one action per step, the observed result and the expected behavior. Include the account type or browser only when it changes the result.
Check before you finish
Use a disposable test example where possible. Replace private content with a short synthetic phrase that still reproduces the failure.
Evidence to keep: Compare the source words with the formatted draft and make sure meaning, names, dates and commitments remain intact. This page’s key limit is: Record how to reproduce a product issue and keep predicted outcomes separate from observed results.
Start here
A ticket is useful when another person can rerun the same steps. Keep version and platform next to the reproduction rather than putting them in a separate verbal tangent.
Speak each step as an action
Say the starting state, one action per step, the observed result and the expected behavior. Include the account type or browser only when it changes the result.
Check exact fields before filing
Verify build numbers and labels against your device. Paste the reviewed text into a draft and use the issue system’s actual fields for environment, severity and components.
Protect test data
Use a disposable test example where possible. Replace private content with a short synthetic phrase that still reproduces the failure.




