/qa-api

Phase: 3 - Design
Domain: API
Command: /qa-api
Prerequisite: qa-plan.md must exist
Allowed tools: mcp__democratize-quality__*, Read, Write

---

What it does

Builds a comprehensive API test plan by reading your OpenAPI/Swagger or GraphQL schema via the democratize-quality MCP server. The plan covers every endpoint in scope (as defined in qa-plan.md), not just happy paths.

---

Test categories generated

Category	Examples
Happy path	Valid requests returning expected responses
Authentication	Missing token, expired token, wrong scope
Input validation	Required fields missing, wrong types, boundary values
Error responses	400, 401, 403, 404, 409, 500
Schema validation	Response body matches declared schema
Edge cases	Empty arrays, null values, maximum string lengths

---

How it works

1. Reads qa-plan.md to confirm API is in scope and identify which endpoints to test
2. Reads dq-qa.config.json for api.schemaUrl and api.baseUrl
3. Invokes the democratize-quality MCP server to parse the schema
4. Generates a structured test plan as qa-reports/api/api-test-plan.json
5. Summarises the plan in a human-readable format in chat

---

Output

qa-reports/api/
  api-test-plan.json     ← machine-readable plan consumed by /qa-exec

---

Execution

The test plan generated here is executed by /qa-exec, which submits it to the democratize-quality MCP server for automated test running.

---

Self-healing

If your schema changes between cycles and the plan becomes outdated, the MCP server detects the mismatch during execution and proposes updated assertions. You are shown the diff and asked to confirm before any test file is updated.