See what your testers are doing

Once your QA testers are working, you'll want to know what they did: how much time they spent, which bugs they found, which fixes they passed, and which ones they sent back. Here is where each of those shows up — and who gets told.

Tested today, and what is left: Overview → Team

Each tester's row on Overview → Team starts with Today: N tested · M left to test:

• N tested — fixes they gave a Pass or Fail today (IST). It is the same number they see on their own Today card, so you don't have to sign in as them to check. Green once it is above 0. A fix with several reports counts once, when its last report gets a verdict.
• M left to test — the fixes on their To verify list right now. Amber when anything is waiting. It drops as soon as they press Pass or Fail.

Below it, what they tested in the last 30 days, e.g. 30 days: 655 tested, 649 pass, 6 fail.

On Members → Testers, sales reps & editors the same waiting count shows as N waiting to test.

Time and bugs filed: Tester Activity

Open Tester Activity in the left sidebar (owners only). One row per tester:

• TESTER — name and email;
• WORK TIME · TODAY — time signed in to the Glitchgrab Chrome extension with Chrome open, today (IST);
• LAST 7 DAYS — the same, over the last 7 IST days;
• BUGS FILED · ALL TIME — every bug they reported, however they filed it: from the Chrome extension, the dashboard chat, the AI report sheet, a public link or an AI agent (MCP). It should match the number under their name on the Reports page.

A break of more than 5 minutes (laptop asleep, Chrome closed) doesn't count. — means no time in that period. The note under the table gives the date counting started; sign-ins before it aren't counted.

Work time counts what testers do through the Chrome extension. no tester activity yet means no tester has used it yet.

This page only shows activity. To add a tester or change their repos, go to Members → Testers (see Add a QA tester).

Fixes they verified: on the GitHub issue

Every verdict a tester gives is written onto the GitHub issue itself, so anyone watching the issue — you, the developer, the assignee — gets GitHub's normal notification.

Tester presses	What happens
Pass	The issue is closed (if it was still open), labelled qa:passed, and a comment is added: ✅ QA passed — [TESTER: name] verified this fix works. with the tester's note (if they wrote one) and their screenshot.
Fail	The issue is reopened for rework, labelled qa:failed, and a comment is added: ❌ QA failed — [TESTER: name] verified this fix and it is not working. with what isn't working and their screenshot. The developer also gets a WhatsApp message (below).
Skip	Nothing changes on GitHub. The check leaves their queue.

A reporter who taps No, reopen on the WhatsApp It's fixed. Did it work? message gets the same result: the issue is reopened and labelled qa:failed. An issue never carries both labels — the newer verdict replaces the older one.

A fix with several reports

An issue that collects several reports from one page (title like [/dashboard/projects] 4 reports) is verified one report at a time. Each Pass or Fail does three things:

• adds its own comment naming the report, e.g. ✅ QA passed — report 2: …;
• ticks or clears that report's box in the issue's checklist;
• on Fail, reopens the issue and messages the developer straight away.

The issue closes and gets qa:passed only when every report has passed.

Who gets a WhatsApp message

• When a fix fails QA, the developer is messaged: ⚠️ Tester <name> says "<issue>" is NOT fixed on <org>. It has been reopened on GitHub. with a View on GitHub button.
  • "The developer" is the GitHub user the check belongs to, if they have a verified WhatsApp number in Glitchgrab.
  • Otherwise the repo owner is messaged instead.
• When fixes are sent for testing, the tester is messaged with how many are waiting and a button that signs them straight in.
• In the evening, a tester with fixes waiting who has verified nothing that day gets one reminder (see Add a QA tester).
• Every evening at 8 pm, each app owner (your client, under Members → App owners) gets the day's numbers for their apps, including how many fixes were sent for verification and how many were verified (see Get WhatsApp alerts for your issues).

Passes do not send a WhatsApp message — the closed issue and its comment are the record.

To receive these, add your number in Settings → WhatsApp notifications (see Get WhatsApp alerts for your issues).

A quick weekly review

1. Overview → Team — check each tester's Today line; a big left to test means they are backed up.
2. Tester Activity — check each tester's last 7 days and bugs filed.
3. On GitHub, filter your repos by the qa:failed label — fixes that came back.
4. On Reports, filter to the tester source to read what testers reported.