Report a bug as a tester

As a QA tester you can report a new bug any time — not only when verifying a fix. Reports file into the repos your admin assigned you.

Before you start

• You have signed in as a tester — from your QA link, or at glitchgrab.dev/login → Tester with your phone number. See Add a QA tester.
• Your admin has assigned you at least one repo.
• The Glitchgrab Chrome extension is installed — add it from the Chrome Web Store. It reports bugs in websites, in Chrome.

Report a bug

1. Make sure you are signed in to Glitchgrab in the same Chrome profile the extension is installed in (open your QA link, or the tester dashboard).
2. Go to the page with the problem and press ⌘⇧G (Mac) or Ctrl+Shift+G (Windows).
3. Pick the project under Project (Choose a project), or check it says Filing to <repo>.
4. Describe it and press Send Report — the dialog is the same one described in What your users see when they report a bug.

The extension attaches your last 50 steps on the site — clicks, field changes, pages opened — so the developer can see how you got there. What you typed is never included.

On a website that already has Glitchgrab's report button built in, ⌘⇧G opens that site's own dialog instead — use it; it files into that site's repo.

Recording a client call from Google Meet? The same extension does that — see Send the bot to a call.

Messages you may see

• No repos assigned to you yet — ask the org owner to add you as a tester or connect a repo.
• No active login — open a QA link or the dashboard first, then try again. — the extension could not find your sign-in in this Chrome. Open your tester dashboard (glitchgrab.dev/login → Tester) or your QA link in the same Chrome profile, then try again. No need to reload the page you are reporting from.
• Sign in to record this call (inside Google Meet) — same cause. Press Sign in, then go back to the call without reloading it. See Send the bot to a call.
• Your Glitchgrab session has expired… — sign in again.
• Pick a repo first — choose the project before sending.

After you send

The report becomes a GitHub issue on that repo. When a developer fixes it and the fix is merged, it comes back to you in To verify.