Make the bug reproducible. Before you hand it over.
Record the browser steps while you reproduce the issue. Add what you expected, point to what failed, and give engineering a replay they can inspect alongside your QA bug report.
Free extension for desktop Chrome. Try it before signing up.
The quote uses two seats even though three are shown.
Select a moment to see how the mismatch develops.
- YOUR QUESTION
- Can someone follow the same steps?
- KEEP THE CONTEXT
- Starting state + actions + expected result
- GIVE YOUR TEAM
- A bug report engineering can investigate
You found the bug. Keep the path to it.
A screenshot shows the failure. A useful reproduction also explains where you started, what you did, and what should have happened.
Try the interactive recording- 01
Start from a known state.
Use a reproducible account and suitable test data. Start recording before you repeat the issue, so the earlier clicks and page changes are part of the evidence.
- 02
Mark the mismatch.
Replay the steps, inspect the affected button or field, and add a note with the expected and actual behavior. Include any setup the recording cannot show.
- 03
Give engineering a path to review and retest.
Share the recording with the bug report. A generated Playwright draft can help start a repeatable check; an engineer still completes the setup, assertions, and run.
Useful for your next test.
A few useful answers.
Know what you can capture and how to share it.
Recording privacy & accessDo I need to write code to record a bug?
No. Start the extension in desktop Chrome, repeat the workflow, and review the recording. You can inspect an affected element and add a note without writing a test.
What should I add to the recording?
Describe the starting account or test setup, your expected result, the actual result, and whether you can repeat the issue. Use sample data and review captured content before sharing.
Can I turn the reproduction into an automated check?
You can export a Playwright draft as a starting point. It still needs the right setup, fixtures, selectors, and assertions, followed by a real test run. Samelogic does not certify a fix from a recording alone.
Your next bug report. The steps already included.
Record the steps. Review what happened. Give your teammate the context to begin.