A QA bug reporting tool that answers the developer's questions up front
Updated
Midge is a QA bug reporting tool built as a Chrome extension. A tester records the bug, and the report arrives with the video, the steps taken, console errors, network requests and environment details already attached, so the developer has what they need on the first read. Midge is free: unlimited recordings, videos up to 15 minutes, and no watermark.
The cost of a bug report is rarely the time to write it. It is the round trip that follows: "Which browser?", "Can you send the console?", "What did you click before that?". Midge is designed to remove that round trip.
What each report already contains
Every recording includes console logs, network requests, user actions and device info. For a QA team that maps onto the sections of a good defect:
| Defect field | Where it comes from in Midge |
|---|---|
| Steps to reproduce | User action log: clicks, page changes, fields typed in |
| Actual result | The video or annotated screenshot |
| Error details | Console errors and stack traces, failed network requests |
| Environment | Browser and version, OS, window size, language, time zone, URL |
You still write the title, the expected result and anything the recording cannot know, such as the test data you used. Our bug report template shows a format that works well with a Midge link.
Repro steps without retyping them
When you record, Midge logs what you do: "Clicked Add to cart", "Navigated to /checkout", "Typed in input[name=coupon]". The typed text itself is never recorded, so test passwords and card numbers stay out of the report. That action log is the outline of your steps to reproduce. Turning it into a numbered list for the ticket takes a minute, and it is accurate because it was recorded rather than remembered.
Each report also gets an AI summary with steps to reproduce and the likely cause, written from the recording and its logs. Every person gets 30 summaries a month for free. Check them against the action log before you paste them into a ticket.
Environment info, captured automatically
"Works on my machine" usually means the environments differ. Midge records the browser and version, operating system, window size, language and time zone with every report. A layout bug that only appears at 1280 pixels wide, or a date bug that only appears in the Europe/Berlin time zone, shows its cause in the info panel.
Errors you did not have to catch
Testers should not need DevTools open to file a good bug. Midge listens to the console and network in the background and keeps the last few minutes in memory, so when something breaks you can start recording or take a screenshot and the error is already there. See console logs and network logs for what is captured.
For flaky bugs that show up once in twenty runs, turn on instant replay for your staging site. When the bug appears, one click saves the last 30 to 120 seconds of the page. Replay is off by default and you enable it per site.
Folders per release
Reports live in a shared workspace with folders. A common setup:
- one folder per release, such as
Release 4.12, - a standing
Regressionfolder for bugs that came back, - a
Needs infofolder for reports waiting on product.
Each report can be shared with anyone who has the link, only with workspace members, or kept private while you finish it. Teams, folders and private reports are free.
A regression run with Midge
- Before the run, create a folder for the build you are testing.
- Work through your test cases as usual. When one fails, record it with the screen recorder or take an annotated screenshot.
- Give the report a title that names the symptom: "Saved filters disappear after logout".
- Send the report to your tracker. With the Jira, Linear or GitHub Issues integration connected, Send to Jira (or Linear, or GitHub) opens an issue with the link, the AI summary and the steps to reproduce. If you use another tracker, paste the link; it carries everything.
- At the end of the run, the folder holds every failure from that build in one place.
Safe to share outside the team
QA often works in staging with real-looking data, and bug reports travel: to developers, to contractors, sometimes to a vendor's support desk. Passwords, card numbers, tokens and cookies are redacted in your browser before anything leaves your device. Emails are half-masked, so [email protected] becomes q***@acme.com. If a vendor asks for a HAR file instead, clean it first with the free HAR sanitizer.
Limits worth knowing
Midge captures Chrome tabs with the extension, and Midge for Mac records Safari tabs and Electron apps with their console and network logs. Firefox runs still need another way to capture evidence; our guide explains how to get a HAR file in each browser. Midge also does not run test cases or track coverage. For an overview of the tools that do, read our guide to QA testing tools.
Frequently asked questions
- How does Midge help with steps to reproduce?
- Midge records your clicks, page changes and the fields you typed in, without the typed text, on the same timeline as the video. That log is a ready outline of the steps, which you can tidy into the ticket in a minute.
- What environment details are captured?
- Browser and version, operating system, window size, language, time zone and the page URL, captured automatically with each report.
- Can we organize reports by release or sprint?
- Yes. Workspaces have folders, so a team can keep one folder per release, per sprint or per test cycle. Teams and folders are free.
- Does Midge replace our test management tool?
- No. Midge captures and shares bug evidence. Test cases, runs and coverage still belong in your test management tool, and the Midge link goes into the defect you file there.