QA Wrap bridge

🧪 QA-Wrap

Test the page. Get the bug report.

🔒 Nothing leaves your computer until you send it to Jira, a tracker or a webhook.

QA-Wrap is a free, open-source bug report extension for QA testers. It records a manual test session, links every failure to the action that caused it, and writes the bug report for you. No account, no server. العربية

🌐 Website · ⬇️ Download · 📥 Get it · ⚖️ Compare · ❓ FAQ · 🚀 Install · 🔄 Updates · 🔒 Privacy · 🧰 More tools

⚡ In 10 seconds

• 🎯 What: a browser extension that records your test and writes the bug report.
• 🙋 Why you: you test web pages and are tired of retyping steps and hunting for the click behind each failure.
• 🔒 Safe: everything stays on your computer until you send it to Jira, a tracker or a webhook.

📥 Get QA-Wrap

Also submitted: Glama, mcpservers.org, mcp.directory, awesome-mcp-servers and Cline marketplace, all waiting for review.

🛠️ What it does

• 🎬 Records a session: you press Start, test as usual, press Stop. Clicks, typing (sensitive values removed), page errors and network failures are kept in order.
• 🔗 Links each failure to its cause: the report shows the action just before every problem.
• 📝 Writes the report: one press copies a ready bug report (title, steps, what happened, evidence). Sending to Jira and other trackers is one button away.
• 🌍 Arabic and English, right to left where it should be.

🎞️ Watch the 40-second film

⚖️ QA-Wrap vs Jam, Marker.io, BugHerd and Bird Eats Bug

All five report a bug from the browser. They differ in what it costs to start, whether you can read the code, and where the recording lives.

From each tool's own home and pricing pages, read on 24 October 2026. Plans change, so check their pages.

• 🏠 Pick a hosted tool when your team wants share links anyone can open.
• 🔒 Pick QA-Wrap when the recording has to stay on the tester's machine, or when you want to read and change the code.

📄 The full comparison

❓ Questions

• 💸 Is QA-Wrap free? Yes. No paid plan, no account, MIT licence.
• ⚖️ Is it a free alternative to Jam, Marker.io or BugHerd? Yes, when the recording has to stay on your machine. Those are hosted services that share reports through their cloud. QA-Wrap has no server.
• 🎫 Does it file bugs to Jira? Yes. File to Jira drafts the summary, maps severity to a Jira priority and lists what is sent and what is not. Other trackers and webhooks are set up in Settings.
• 🌐 Which browsers? Chrome and Edge are the tested browsers (Chrome 116 or newer). Edge users install it from Microsoft Edge Add-ons. The Firefox listing is in review.
• 🤖 Can a coding agent read the reports? Yes, through qa-wrap-bridge, a read-only MCP bridge. It stays off until you turn on Agent bridge in Settings.
• 🌍 Arabic? Yes. The interface and the reports come in English and Arabic.

🚀 Install (about 3 minutes, once)

The Chrome install loads the release zip by hand because QA-Wrap is not in the Chrome Web Store. Chrome only allows that with Developer mode switched on. It is a normal Chrome switch and installs nothing by itself.

You need a Chromium browser at version 116 or newer. Chrome and Edge are the tested browsers; the others below work the same way. Windows, Mac and Linux are supported.

🌐 Other browsers (Edge, Brave, Opera, Vivaldi, Arc, Yandex, Firefox, Safari)

The updater step registers itself for every browser it finds on your computer and tells you which. Each browser updates to its own zip, so an Edge install never receives the Firefox build.

Firefox: the Firefox Add-ons listing is in review (submitted 2026-10-23), so Firefox users wait for it. The table zip still works, but it loads only until Firefox restarts.

Safari is not packaged. It needs a Mac with Xcode to turn the build into an app (xcrun safari-web-extension-converter), and one-press update is not available there.

1. Open the latest release.
2. Under Assets, click the zip for your browser from the table (the Chrome one is qa-wrap-VERSION.zip). It lands in your Downloads folder.
3. Make a folder where it can stay, for example C:\QA-Wrap. Do not use Downloads: if the folder is deleted, QA-Wrap disappears from Chrome.
4. Right-click the zip, choose Extract All..., pick that folder, press Extract. Open the folder and check that manifest.json is directly inside it.
5. In Chrome, type chrome://extensions in the address bar and press Enter.
6. Top right, switch Developer mode on.
7. Press Load unpacked, choose the folder from step 3, press Select Folder. QA-Wrap appears in the list.
8. Turn on automatic updates (once), so updates install by themselves. Open the folder from step 3, then open the folder called updater inside it.
   • Windows: double-click install.cmd. A black window shows five short steps in English and Arabic and says Done.
   • Mac or Linux: open the Terminal app, type bash (with a space after it), drag the file install.sh from the updater folder into the Terminal window, press Enter.
   • It needs no admin rights and installs nothing else. It is safe to run twice.
9. Click the puzzle-piece icon in the Chrome toolbar and the pin next to QA-Wrap. Open any page, press the QA-Wrap icon, then Wake up, name what you are testing, Start, and Stop when done.

Chrome may show "Disable developer mode extensions" when it starts. Press the X; do not press Disable.

Keep the folder where it is. The update replaces the files in that same folder, so QA-Wrap keeps its identity and everything you recorded.

🔄 How updates work

Each time Chrome starts (and then once a day), QA-Wrap asks GitHub whether a newer release exists. It sends nothing about you or your tests. If there is one, a small Update card appears in the QA-Wrap popup and in Settings. It never blocks you.

• Update: Chrome asks once for permission to talk to the updater from step 8. Allow it, and QA-Wrap downloads the release, checks it, swaps the files in your folder (keeping one backup copy beside it, and rolling back by itself if anything fails), reloads, and opens "What's new in this version". You do nothing else.
• Not now: the card stays away until the next Chrome start or the next version.
• Your sessions, recordings, notes and settings are stored in your Chrome profile, not in the extension folder, so an update never touches them.
• Skipped step 8, or declined the permission? Update then downloads the zip and shows three steps: extract it over the same folder, open chrome://extensions, press Reload on QA-Wrap.

🔑 Optional: forks and private mirrors

Optional, for forks and private mirrors. If you run QA-Wrap from a private fork, GitHub hides its releases from anyone not signed in, so the check stays silent unless you give it a key. In QA-Wrap Settings > Check for updates, paste a read-only GitHub token (a fine-grained token with Contents: read-only on that repository). The public repository needs no token. It stays in your browser profile, is shown masked, and is sent only to GitHub. Remove it any time. The check can be switched off in the same place.

🔒 Privacy

• Everything QA-Wrap records stays in your browser on your computer.
• Nothing is sent anywhere until you press a button that says so (for example Send to Jira).
• The one automatic request is the update check above: a plain read of the release list at api.github.com/repos/NJ-Burrito/QA-Wrap, with no cookies and no personal data.
• Passwords, tokens and similar values are removed from what is recorded.

Details: PRIVACY.md (العربية).

🆘 Problems?

Open an issue in this repository, or see the portfolio at https://nj-burrito.github.io.

👩‍💻 For developers

Run from source: chrome://extensions > Developer mode > Load unpacked > pick extension/. Tests: cd extension && npm test. Release zip: npm run release:zip (writes dist/qa-wrap-<version>.zip). Pushing a tag vX.Y.Z that matches extension/manifest.json publishes the release through .github/workflows/release.yml. The release attaches qa-wrap-<version>-<dist>.zip plus .sha256 for every browser build, and qa-wrap-<version>.zip (the Chrome build) as the alias older installs look for. The updater host is extension/updater/ (PowerShell on Windows, bash on Mac and Linux; install.cmd and install.sh register it for each browser found).

👤 About

• 🎯 What it is: a free browser extension for manual testers. It records a test session and writes the bug report.
• 🙋 Who made it: Nader Alzghoul, a QA automation engineer in Amman, Jordan.
• 📜 Licence: MIT. The source is public and third-party parts keep their own licences.
• ✉️ Contact: naderalzghoulbusiness@gmail.com
• 💼 Portfolio: Nader's work and projects, with the contact section
• 📦 NJ-Kit: skills for Claude Code
• 🪪 Profile-Wrap: your profile as a page
• 🐙 GitHub: the source and all the open repositories
• 🔗 LinkedIn: Nader's profile

Copyright (c) 2026 Nader Alzghoul. Released under the MIT licence. Third-party components keep their own licences: see THIRD-PARTY-NOTICES.md.