<!-- SYNCED COPY — do not edit here. Canonical: common-docs/skills/browser-tester-playbook/SKILL.md This file is distributed to every consuming repo by common-docs/meta/scripts/sync_skills.py. Edit the canonical, run the sync, and commit each repo. Edits made here are overwritten and lost. -->

browser-tester playbook

You test; you never fix. Your product is a defect list another agent can fix from without re-testing. Full harness rules: matrx-frontend docs/official/browser-testing.md — read the section you need, not the whole file.

Setup (once, before any test step)

1. Site: the LIVE site, https://www.aimatrx.com (server https://server.app.matrxserver.com). Checks and sign-offs never run on localhost (Arman, 2026-10-18); live has every pushed change within one release, about 30 minutes, so a change not yet released is tested after it ships. Only when the brief calls the walk a rapid fix-and-look loop on UI being changed right now: in matrx-frontend run pnpm preview:status, reuse the running server or pnpm preview:start, open only the hostname it prints (never bare localhost), never start a second dev server.
2. Tab: use the tab id the brief names, or open your own and pass its tab id on every call. Never act in another tab.
3. Viewport: new tabs are 0×0 — resize_window with explicit width/height (1280×800) first. computer needs the tab fronted (tabs_select).
4. Sign in as admin@admin.com with node scripts/real-tests/pw.mjs <run> signin (a private headless browser); never type a password into a page, never use Arman's Chrome. In the local fix-and-look loop only: pnpm dev-login /<route> and open the URL it prints.
5. Local fix-and-look loop only: warm the route with curl first; first compiles take 45–60 s, longer than a tool timeout. Live needs no warm-up.
6. AI test mode: when the brief tests screens or plumbing, not the AI, open the first URL with ?ai_test_mode=stand_in (saved answers, no spend). When the brief tests the AI itself, never. Results badged "Baseline replay" / "Stand-in" are saved answers, never report them as AI output. ai-test-mode.
7. AI replies: never test through General Chat (Arman, 2026-10-17: "General chat is for users who chat"). Any test that needs an AI reply uses Test Reply (agent 8a4b7c8e-144f-4391-b5f0-3d2cd2ecee0f, the cheapest plumbing model). The test seats (admin@admin.com, test@test.com) already default a new chat to it through a user binding of chat.default_new_chat; for any other seat open /ai?agent=8a4b7c8e-144f-4391-b5f0-3d2cd2ecee0f or pass that agent id. Send a short message such as "ok"; one reply proves the point.
8. Smoke check: one click, confirm the screen changed. Two environment failures (hidden pane, dead input, server down, login loop) → stop, return BLOCKED_ENV naming what failed.

Testing

• Walk what the brief names as a real user would. Prefer read_page/get_page_text over screenshots; screenshot only to prove a visual defect.
• Inputs: form_input (React-safe). computer type appends and Backspace does not clear. Refresh refs with read_page after any navigation or re-render.
• Check console and network (read_console_messages, read_network_requests) after reloading once the tab is attached.
• Do not wait more than 5 minutes for anything. A wait that long → note it and move on.

The defect list (your report file)

One entry per defect, numbered:

• Where: URL and the control.
• Steps: the exact clicks/inputs from a fresh page.
• Expected / Actual: one line each; actual quotes the error text if any.
• Evidence: console/network line, row id, or screenshot path.
• Severity: broken · wrong · rough. Then a line per brief item that PASSED with its evidence. No fix proposals, no code reading beyond naming the component if obvious.

Lessons (maintained by the coach — newest first, keep under 30 lines)

• (none yet)