Repros

Record structured QA test sessions: console errors, failing requests, clicks and screenshots captured automatically as you test.

Repros turns manual testing into bug reports that bring their own evidence. Start a test session for a change (a feature, fix or tweak) and build, then test the way you normally would. While you do, Repros records what the page was doing — so when something breaks, the developer gets the console error, the failing request, the steps that led there and a screenshot, not "it didn't work, can you reproduce it?" WHAT GETS CAPTURED, AUTOMATICALLY • Console errors and warnings — with the line of code that logged them • Uncaught exceptions and unhandled promise rejections, with stack traces • API requests and every failing request (4xx, 5xx, connection errors) with method, URL, status, timing, headers and payload • Clicks and page navigation, turned into numbered steps to reproduce • Screenshots — on demand, attached to your notes, and automatically when an error fires • Browser, OS, window size, language and timezone Sensitive values are redacted in your browser before anything is uploaded: authorization and cookie headers, fields that look like passwords, tokens, secrets or card numbers, and card- or SSN-shaped values wherever they appear. Clicks record which element was clicked — never what was typed into it. A TOOLBAR THAT STAYS OUT OF THE WAY • A compact recording panel on the page under test, with a live timer and error counts — minimise it to a pill when you need the space • Press N to jot a note, pick a severity (Blocker, Major, Minor, Cosmetic) and a screenshot is attached for you • Work through the change's checklist as you go • Stop, then pass or reject with notes — or resume testing, or discard a session started by mistake ASSIGNED WORK, ONE CLICK AWAY Developers assign a change and build to a tester from the Repros dashboard. It appears in the extension with a desktop notification; one click opens the right build with capture already running. When the tester signs off, whoever assigned it is notified with the result. FOR DEVELOPERS: A REPORT, NOT A TRANSCRIPT Every session becomes a report in the Repros dashboard that leads with what went wrong — the tester's notes by severity, each distinct error once with its count and stack, each failing endpoint once with its payload — followed by auto-written steps to reproduce and the full, searchable timeline. • Copy the whole report as a Markdown bug report for GitHub, Linear or Jira • Copy any captured request as a cURL command • Share a read-only link with someone outside your workspace PRIVACY BY DESIGN Repros only records while you have a session running, and only on the domain of the project you're testing — never your other tabs, and never in the background. Your organisation proves it owns a domain before a project can point at it. HOW TO GET STARTED 1. Create a workspace at https://repros.dev (free 30-day trial, no card required) and add a project for your app's domain. 2. Install this extension and sign in. 3. Open a change assigned to you, press Start testing, and test. Repros requires a Repros account. The extension is free; workspaces are billed per team.