Class: verify an app's behaviour, not its appearance — routes, persistence, domain rules, and authorisation. The deliverable is a report where every claim carries raw evidence (status code, body type, DB row, scenario output) plus a numbered bug list. "Everything returned 200" is not a result.
select count(*) per table. A seed that
"ran with no errors" proves nothing about what landed.npm run build, then the local runtime with the DB bound).
QA the production bundle, not a dev server with different wiring.SELECT.no such table. Diagnose by diffing which file each command touches, then seed the file
the server actually opens and re-assert row counts through a live /api/... call, never
through the seeding CLI./* /index.html 200 rule answers
GET /api/products/<slug> with HTTP 200 and an HTML body; a status-only sweep scores it green.
Check Content-Type (or isinstance(body, dict)) on every JSON route.JSON.parse coerces digit-only strings into numbers. A settings reader that parses stored
values returns whatsappNumber as an int; the frontend's .replace() then throws and the whole
SPA renders blank while every endpoint still 200s. Audit types, not status codes:
bash
curl -s localhost:8788/api/settings | python3 -c \
"import sys,json;d=json.load(sys.stdin);[print(f'{k:18}{type(v).__name__:8}{str(v)[:40]}') for k,v in d.items()]"
A blank SPA with green endpoints is this bug until proven otherwise — the browser-side recipe
(probe page, empty console message, fetch interception to prove causality) is in web-visual-qa
→ "Blank SPA".total of 1 for a 1,450-EGP item, and a coupon code that does not exist — both
were accepted and persisted as-is. Re-read them from the DB; the API's own success response is
self-serving evidence.expiresAt and usageLimit still
yielded the discount. For every field in a type, either find its reader or report it as
unenforced — a contract field that nothing checks is a bug, not a fixture.reasons array was always empty, contradicting its own interface doc. Assert
on the explanation output, not just the chosen item.POST /api/admin-* route with no token (401),
with a forged token (401), and with a token obtained from a real login (200). One wrong-answer
login plus one right-answer login proves both branches.#9–#15 and pasted those links into
the report; an earlier audit had already taken #9 and the real range came back #10–#16, so the
delivered report shipped wrong URLs until I patched it. Create first, read the URLs the CLI prints,
then write them into the report.dist/ / the build output for testing must be on the teardown checklist, not left to memory.Endpoint table (method · path · expected · status · body type) · domain-scenario table (input →
chosen id → score → explanation) · E2E with the DB SELECT as proof · then a numbered bug list
ordered by severity, each with reproduction, observed, expected, and evidence path. State
explicitly what passed and what went untested rather than implying full coverage — an honest
partial report beats an overclaimed complete one.
The bug list is only delivered when it is filed and the session is clean. Order matters:
--body. One /tmp/qa-issue-<n>.md per bug, then
gh issue create --repo <r> --label agent --title "…" --body-file /tmp/qa-issue-<n>.md.
Long bodies with backticks, JSON and Arabic make inline --body "…" quoting hell. Wrap the
creates in a shell function with an echo "--- <n> ---" marker before each one so the URL each
call prints maps back to the right bug.gh issue list --repo <r> --label agent --state all — the count must equal security + functional.bash
rm -f dist/qa-probe*.html # probe pages in the build output ship next deploy
kill <verified-own-pid> # only a process you started
Then a fresh call: ss -ltn | grep <port> and pgrep -af wrangler. Confirm the verified process has stopped.Evidence from real runs: references/elfiky-store-run.md (sweep + scenario + server-authority
templates and results) · references/closeout.md (issue filing loop, bug→issue map, report shape,
teardown transcript and the pkill trap).
Screenshots, viewport/RTL audits, layout and console-error forensics for the same app →
web-visual-qa. Whole-stack behaviour, types, authorisation and persistence → here.