Add a QA tester

A QA tester is someone — often on your client's staff — who checks fixes and reports bugs without a GitHub account. They sign in with their phone number, see only the repos you assign them, and verify each fix with Pass or Fail.

Before you start

• You are the org owner.
• You have the tester's mobile number (Indian +91 numbers — the sign-in code is sent by SMS).

1. Add the tester

1. Open Members in the left sidebar and go to the Testers section.
2. Press Add tester. The Add a tester panel opens.

3. Fill in:
   • Name (required)
   • WhatsApp number — Used for OTP login + notifications.
   • Email (optional)
4. Under Assign repos, tick every repo this person should test. They will see nothing else.
5. Press Add tester. You will see Tester added.

2. Get them signed in

Either:

• Send the QA link — on the tester's row press Copy QA link (QA link copied) and send it to them. Opening it signs them straight in. Treat it like a password — anyone with the link is signed in as that tester.
• Or let them sign in by phone — they go to glitchgrab.dev/login, choose the Tester tab, enter their number, press Send code by SMS, type the code and press Verify and continue.

3. Change a tester later

On the tester's row:

• Edit → change their details or assigned repos → Save changes.
• Trash icon → Confirm to remove them.

Assigning repos happens only here, on Members → Testers. The Tester Activity page only shows what testers have done.

What the tester sees

After signing in they land on their own dashboard with:

• Overview — what is waiting for them, what they verified, and Issues filed: every issue created on their projects each day over the last 14 days, and how many today.
• To verify — fixes to check. Click a fix to open its panel: The bug (what was reported, with its screenshot) comes first, then What was fixed, then the Full issue. For each: Pass (attach a screenshot or file of the testing, then Confirm pass), Fail (say what is not working, attach a screenshot or file, then Confirm fail), Skip, or a comment. Pass, Fail and comments each take up to 5 attachments — screenshots, or text files such as a saved .html page: pick several at once, add more one at a time, or paste a screenshot with ⌘V / Ctrl+V. On the GitHub issue an .html file opens as the page itself, in a safe sandboxed viewer.
• History — what they have verified.
• Calls — recorded calls on their repos.
• Report bug in GlitchRecord — file a new bug from the desktop app. See Report a bug as a tester.

How fixes reach them

A check appears in To verify when:

• a pull request that closes an issue is merged, or
• you press send to qa on a report (see Find and manage reports).

When they press Fail, the issue is reopened and the developer is notified — Marked as failed — developer notified. Pass marks it verified.

The merge already closes the issue on GitHub, but the check stays in To verify until the tester presses Pass. Its panel says so (Already closed on GitHub when PR #N merged), and the fix's number shows as PR #N so it isn't mistaken for another issue.

Evening reminder on WhatsApp

At 6:30pm IST, a tester with fixes waiting who has verified nothing that day gets one WhatsApp reminder with Verify now and Skip today. It is sent at most once a day and never when their queue is empty. Skip today silences it until tomorrow.

Troubleshooting

• The tester cannot see a repo — it is not assigned. Members → Testers → Edit → tick the repo → Save changes.
• "Invalid code" — the code was mistyped or expired. Press Use a different number and request a new one.
• No code arrives — check the number is the one on their tester row. Codes go by SMS, not WhatsApp.
• A fix you already passed is still in To verify — another tab or window has an old copy of the queue. Press Pass, Fail or Skip on it, or open it: it disappears with Already passed — removed from your queue. Nothing is filed twice.