🧪 Tester start page for testers
Scenario guide S1–S12 (English + Tagalog toggle), the start-interview button on the dedicated tester role, and "report my last interview" for stuck calls. This is the only link testers need.
Open test bed🗞️ Daily brief write & publish
The day's focus, written in English + Tagalog. Publishing pops it up on the test bed for every tester who hasn't acknowledged it, and shows you who has read it and who hasn't. Yesterday's briefs stay in the archive as the day-by-day record.
Write today's brief📚 Brief archive for testers
Every published brief, newest first, with the asks made that day and the full analysis behind them. This is the reference testers are pointed at from the popup.
Open archive📊 Live QA dashboard realtime
Per-tester productivity, scenario coverage matrix (covered vs left), issue analytics, quality-by-build, implicit machine signals, and QA-review progress. Auto-refreshes every 30 seconds.
Open dashboard🎧 QA review console QA lead
Odette's second-layer review: score each interview's conduct quality and transcript accuracy (1–5), with inline transcript viewer and recording-reviewed flag.
Open review console📝 Report form per interview
The structured debrief testers file after every call (roster dropdown, scenario code,
issue taxonomy, severity, environment). Normally reached from the interview page —
this direct link needs an ?interview_id=….
📄 Data export
All reports as CSV — one row per report, one column per issue code, joined with machine context (build, duration, end reason). For the final test report.
Download CSV📘 Plan & playbook
QA_TEST_PLAN.md — objectives, roles, coverage targets, quality gates, exit criteria, and the final-report template. TESTER_PLAYBOOK.md — the tester-facing process doc. Both live in the repo root.
View plan