Make the bug
easy to follow.
Record the browser steps that lead to the issue. Replay what happened, inspect the affected element, and give your teammate a clear place to start.
Free extension for desktop Chrome. Try it before signing up.- Open page
- Add seat
- Add again
- Calculate
The second click changes the story.The seat count updates. The quote doesn’t.
See the bug.
Then see what led to it.
Three seats appear on screen, but the quote still uses two. Replay the steps to find the change, then select an element to inspect it.
- 01Replay the clicks
Follow the sequence, including the second “Add seat” click.
- 02Inspect an element
Select a number or button to see its details at that moment.
- 03Add your context
Tag an element and leave a note about what went wrong.
Seat renewal
An interactive example with sample data. Your demo notes stay in this page.
A useful reproduction
starts before the failure.
- 01
Start before the bug.
Open the extension and start recording while the page still works as expected. Include any setup your teammate will need.
- 02
Follow the steps that trigger it.
Repeat the clicks and page changes that lead to the issue. Keep the steps that matter, including a repeated action if it changes the result.
- 03
Stop, replay, and inspect.
Find the moment the result changes. Select the affected element and add what you expected alongside what actually happened.
- 04
Review it, then share it.
Check the recording for sensitive content, choose who can open it, and add its link to your issue so your teammate can investigate.
A little structure.
A lot less back-and-forth.
- Starting point
- Page URL, browser, and any setup needed.
- Steps to reproduce
- The shortest sequence that still triggers the bug.
- Expected result
- What should happen after those steps.
- Actual result
- What happens instead, and where it first changes.
- Recording
- A reviewed recording link your teammate can open.
Paste it into the issue tracker your team already uses.
Does it record all my browsing?
No. You start and stop each recording. Samelogic captures the browser flow you choose; it is not passive or continuous session replay. It cannot show what happened before you started recording.
Can I record a bug without writing code?
Yes. Start a recording in the Chrome extension, reproduce the bug, then stop and review it. You can replay the steps and inspect elements without writing a test.
Do I need an account to try it?
You can install the extension and try a recording in desktop Chrome before signing up. You’ll need an account to save recordings to a workspace and share them.
What should I check before sharing?
Input values are masked by default, but other page content can still appear. Review the recording before sharing it. Private recordings require project access; anyone with a public link can open a public recording. Make it private again to turn off public-link access.
Give your next bug
a clear starting point.
Record the steps. Keep the context. Help your teammate pick up where you left off.