A snag, explained.
Inspect a portable report with an observation, recorded interaction, diagnostic evidence, and reproduction readiness. The structured report is included too.
Open sample bug report →View report JSON →Two reports.
One clearer picture.
A bug report tells the story of a problem. A test-run report shows what happened across a set of checks. Open either sample and explore.
Illustrative sample data. These pages do not run tests or send anything to an external tracker.
Every check has a story.
Explore passing, failing, and retried profile checks. Select a result, inspect attempts and evidence, filter outcomes, or create a local bug-report export.
Open sample test-run report →View run JSON →Keep exploring.
Try the larger report-interface playground, with illustrative result details, comments, filters, and usage views.
Open report design playground ↗Read the results walkthrough →Want to catch your own snag?
The sample app has an intentional profile-save bug to explore.
Try the bug reporter ↗