The bug reporter
A working sample host with the right-edge badger button. Open the drawer, explore capture setup, review, replay, and settings.
Capture and submission are simulated.
Try the reporting button ↗
Small snag. Big adventure.
Catch the snag.
Catch the snag.
Keep the evidence.
That “it broke” moment deserves a better story. Bring bug reports, test plans, and useful evidence together with SnagBadger.
Explore at your own pace. Synthetic data. No account needed.
Oops? We got this.YOUR SMALL BUT DETERMINED QA SIDEKICK
01 / FIND IT
A bug worth catching.
Reproduce a problem in the sample app. Compare the buggy and fixed behavior.
02 / EXPLAIN IT
Keep the useful bits.
Explore reporting, screenshots, recorded steps, diagnostics, and evidence review.
03 / TEST IT
A clearer next step.
Browse test plans and results. Turn a finding into a report you can take with you.
THE HANDS-ON PART
All examples & walkthroughs →
Less reading. More trying.
One app. Two outcomes.
Save a profile, navigate away, and see what sticks. Switch between intentional buggy and fixed behavior.
Session-only sample data; reload to start fresh.
Open the React playground ↗The whole story, in a report.
Inspect a bug report and an interactive test-run report, with result details and supporting evidence.
Illustrative samples, not a live test execution.
Choose a sample report →Record. Inspect. Replay.
Try DOM screenshots, interaction recording, and rrweb replay using the maintained capture adapters.
Screen sharing requires HTTPS and browser permission.
Explore capture & replay ↗Look beneath the surface.
Explore browser and app diagnostics with explicit collection controls. Inspect what gets included.
The static site has no traffic/echo backend.
Open diagnostic collection ↗Try the plain-HTML diagnostics →Small examples. Real APIs.
Run focused reporting and configuration examples on demand, inspect their output, and see the code.
Run the API examples →
A FEW MORE PLACES TO POKE
Follow your curiosity.
Find it. Explain it. Test it.
Start with an example, then bring the pieces into your own workflow.
Find your starting point →