Every manual test session records its own evidence as it happens — console errors, failed requests, and screenshots, timestamped against the exact feature and build being tested. No more "can you reproduce that?"
A tester finds something broken, describes it from memory, and a developer spends the next twenty minutes trying to get back to the exact state where it happened — often unsuccessfully.
None of them do the part that actually matters: a deliberate, per-feature test session that captures its own technical evidence as it runs.
Great for capturing a single bug with some technical context attached after the fact.
Captures everything, always, in production — built for debugging real users after something goes wrong.
Structures what to test and tracks pass/fail — but the tester still attaches evidence by hand, if at all.
The wedge: a structured, assignable, per-feature test session with automatic technical evidence capture built into the session itself — not bolted on, not reconstructed later.
Point it at a domain pattern — app.example.com, or *.preview.example.com for per-PR previews — then add builds and the features to test, each with a description.
On a matching domain, the toolbar appears on its own. Nothing to configure, no separate app to keep open alongside the browser.
Pick a feature and build, or open an assignment sent directly to them. One click, and capture begins immediately.
Console errors, uncaught exceptions, and failed requests log themselves in the background. Testers add annotated notes with severity, attach screenshots, and work the checklist live.
Pass or reject, with notes. A rejected session routes back for retest the moment a new build is ready.
Full per-session timeline, session history per feature, and shareable read-only report links — hand a developer the exact session, not a paraphrase of it.
Console errors and warnings, uncaught exceptions, and 4xx/5xx network failures are captured the instant they happen — timestamped and tied to the session, with zero manual copy-paste.
Any note can carry an auto-captured screenshot for context, plus a severity level — so the dashboard triages itself.
Developer-defined pass/fail items the tester works through live in the toolbar — so sign-off means something beyond "seemed fine."
Assign a specific feature and build to a specific tester. It surfaces immediately in their extension popup — no hunting through a picker to find what to test.
Org-based, independent per member: manage content, test, manage users, view analytics. Restrict a contractor to only what's assigned to them.
A read-only link to one session's full report — hand it to a developer without giving them dashboard access.
The evidence trail doesn't have to stop at sign-off. Two integrations we're building next, closing the loop from "session rejected" straight into your team's existing tools.
The moment a session gets rejected, the right channel hears about it — severity, notes, and a link to the full evidence trail, not just "something broke."
Turn a rejected session into a Linear issue in one click — console errors, failed requests, and screenshots attached automatically, not pasted in by hand.
// Have a tool you'd want us to prioritize instead? Tell us.
All plans start with a free 30-day trial — 5 seats included, no card required.
A Chrome extension and dashboard for structured QA testing. Every test session automatically captures console errors, failed network requests, and screenshots as they happen, tied to the exact feature and build being tested — so bug reports come with their own evidence instead of a guess at what went wrong.
No. There's no SDK to add to your codebase — the extension watches the browser tab being tested, not your application's code.
Starter is £29/month for up to 5 testers, Team is £79/month for up to 20 testers with unlimited features and retention, and Enterprise is custom-priced with negotiated seats and SSO. Every plan starts with a free 30-day trial, no card required.
Yes — the extension itself is free for testers to install and use. Pricing is per workspace, not per install.
Repros is currently a Chrome extension. Other browsers aren't on the roadmap yet.
Slack notifications and a Linear integration are both in development, so a rejected session can notify your team or become a tracked issue automatically, with evidence attached.