/qa-exec

Phase: 4 - Execution
Command: /qa-exec
Prerequisite: All in-scope design skills must have run
Allowed tools: Bash, mcp__democratize-quality__*, Read, Write

---

What it does

Executes all in-scope domain tests in the recommended order. Reads qa-plan.md to determine which domains are active, then runs each one sequentially.

---

Execution order

API  →  UI + Accessibility  →  Performance

This order is intentional:

• API first - validates the backend is stable before browser tests
• UI + A11y together - the UI script and a11y audit run in a single browser session
• Performance last - load tests put stress on the system; run after functional tests confirm it's working

---

Per-domain execution

API execution

Submits the api-test-plan.json to the democratize-quality MCP server:

mcp > democratize-quality > run_tests(plan: "qa-reports/api/api-test-plan.json")

Output: qa-reports/api/api-report.html + api-report.json

UI + Accessibility execution

a11y-cli run qa-reports/ui/ui-test.yaml \
  --output-dir qa-reports/ui/ \
  --a11y-output-dir qa-reports/a11y/

Output:

• qa-reports/ui/ui-report.html
• qa-reports/a11y/a11y-report.html

Performance execution

dq-nbomber run load-tests/dq-nbomber.yaml \
  --report-dir qa-reports/perf/

Output: qa-reports/perf/perf-report.html + perf-report.json

---

After execution

• If failures exist → run /qa-triage
• If all pass → run /qa-coverage (release readiness mode) then /qa-report