Full demonstrations, room to explore#

Capture, reporting and host studies open in their own page. This keeps real browser permission prompts and recording scopes attached to the demonstration rather than a documentation iframe. Opening a page is separate from opting into collection; review its controls before starting.

Maintained host behavior#

• React playground: supported deterministic buggy/fixed profile saves, navigation and reset. It uses session-only data and does not persist a profile. Complete host source and shared scenario.
• plain-HTML host: supported standard DOM interaction, without React. Its optional reporter mount is empty. Complete host source.

Follow the sample-site walkthrough for the exact buggy/fixed comparison and its first test run.

Experimental capture and replay#

Open the capture experiment. Try a DOM screenshot, recorded interactions and rrweb replay. Screen sharing requires explicit browser approval and a compatible secure context; an HTTP preview may report the native API unavailable. Capture fidelity, default screenshot method and sharing lifetime still require human evaluation. This is an experiment, not a production capture commitment.

Use synthetic example data. Capture happens in the demo document, not across this guide. Review the export before sharing; privacy filtering reduces retained content but does not replace a project-owned privacy review. Start, stop and reset using the study controls. Complete maintained capture source and adapter composition.

Experimental diagnostic collection#

Open the React diagnostic study or plain-HTML diagnostic study. Both use the maintained diagnostic experiment with explicit collection and content controls, bounded buffers, visible host outcomes and stop/disposal counters. Collection starts off. Selecting content can retain headers, bodies or messages: use the supplied synthetic traffic and review the collected result.

This design is awaiting human usefulness evaluation. Browser fetch diagnostics deliberately omit response outcomes to preserve the original promise behavior. Static previews may not supply the development-only traffic/echo fixture, so network fixture failures must not be mistaken for production transport support. Complete React source, plain-host source and shared scenario.

Experimental reporting interface#

Open the interactive bug reporter to play with the actual Report a bug button on the right edge. Hover, focus or tap the badger, then try capture setup, start/stop, report review, replay and settings. The host stays usable while the drawer is open. Capture and submission are simulated; this demo does not collect or send your data. Follow the reporter walkthrough for the complete flow and maintained host source.

Open the reporting prototype for the warm-mono caped-badger recording/review study. Its recording controls simulate states; they do not capture a screen or audio, request permissions, upload or submit to a tracker. The separate capture experiment above exercises real adapters. Complete maintained reporting host and prototype limitations.

Return to small API examples, all examples, or the reporting configuration guide.

Experimental test-run report interface#

Open the test-run report prototype to explore a representative run, result details, comments, filters and usage views. This uses illustrative local fixture data; it does not execute the displayed tests or prove a real test outcome. Complete maintained host source and report interface source. For actual run artifacts, follow review results and create bug reports.