QA Skills Library / fullstack-functional-qa

Full-Stack Functional QA

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.

Order of work

  1. Read before you run. Route table, schema/seed, and the domain-engine source. Derive the endpoint list and the scenario list from the code — never from memory or from the README.
  2. Seed the local DB, then verify row counts with a select count(*) per table. A seed that "ran with no errors" proves nothing about what landed.
  3. Build and serve the real thing (npm run build, then the local runtime with the DB bound). QA the production bundle, not a dev server with different wiring.
  4. Endpoint sweep recording status and the runtime type/shape of every body.
  5. Domain scenarios fed by rows fetched from the live API (not hand-typed fixtures) — the fixtures are exactly where a type bug hides.
  6. E2E for the money path: cart → coupon → order. Then confirm with a direct SELECT.
  7. Closeout: file one issue per confirmed defect, then write the report with the real issue URLs, then tear down what you started (probe files, dev server). Details below.

Pitfalls found on real runs — each one costs an hour if you don't know it

Report shape that gets accepted

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.

Closeout: issues → report → teardown

The bug list is only delivered when it is filed and the session is clean. Order matters:

  1. Body files, not inline --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.
  2. Verify the filing, don't assume it: gh issue list --repo <r> --label agent --state all — the count must equal security + functional.
  3. Write the report last. Paste the URLs the CLI actually returned (see the issue-number pitfall above). The report's own issue table should double as the index a fixer reads.
  4. Teardown, and check it in a separate call: 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).

Scope boundary

Screenshots, viewport/RTL audits, layout and console-error forensics for the same app → web-visual-qa. Whole-stack behaviour, types, authorisation and persistence → here.

raw Markdown · all skills