ProtectMyMail — QA Test

How this QA tool works

A guided test for the ProtectMyMail launch. Everyone sees the same live board — your marks and reports appear for the whole team instantly.

Click the ⓘ icon on a case to see Goal · Steps · Expected · If it fails.
Do the test, then mark it for 🖥 Desktop and 📱 Mobile separately: Pass / Fail / Blocked. (Plugin cases are desktop-only.)
Blocked shows a small box to add a short reason.
Clear a mark by clicking it again, or the ✕ button.

Clicking Fail opens the report form. You can also use 📎 Report / attach a screenshot on any case, anytime.
Choose Type: 🐞 Bug (needs severity + steps) or 📎 Note / attachment (just add a screenshot/file).
Fill title + steps (required), severity, who to assign it to, optional URL/version.
Add screenshots/files: drag the picker or just paste with Ctrl/Cmd + V. Your browser/device is captured automatically.
Your typing is auto-saved as a draft — you won't lose it if you navigate away.

Under any case: suggest an improvement. For general ideas: the 💡 Suggest an improvement button at the top.
Suggestions are tracked separately from bugs.

All payment tests use the Stripe sandbox — never real money. Success card 4242 4242 4242 4242, decline card 4000 0000 0000 0002 (any future expiry, any CVC).

Launch-readiness banner (🔴/🟡/🟢), coverage, pass/fail, and all reported items.
Filter by severity, status, platform, assignee, area · Mine only · Group by area (flags likely duplicates).
Every item can be edited or deleted.
Bug status: open → fixed → verified. When a fix lands, the bug shows ↻ re-test; re-test the case, set it to Pass, then mark the bug verified.
Download Bugs (MD) and Suggestions (MD) separately for the final analysis.

That's it — test, mark, report, and we ship a clean launch. Thank you! 🛡️