integration-testslisted

Integration Tests — design-driven, systematic verification for the Integration Sprint. Derives boundary-value, flow-branch, and pattern-branch test cases from the enabled design specs, builds stubs for non-reproducible external interfaces, automates API and UI tests as committed project assets, and records results to .scrum/test-results.json. Runs before UAT & Release.
sohei56/maul-team · ★ 15 · Testing & QA · score 68

Install: claude install-skill sohei56/maul-team

## Inputs - state.json → phase: "retrospective" (entered via `sprint_continuation: integration_sprint`) or already "integration_sprint" on re-entry. - `docs/design/catalog-config.json` — `enabled` array of spec IDs (SSOT for which specs are in scope). - `docs/design/specs/**` — enabled spec files. Per `docs/design/catalog.md`, each lives at `docs/design/specs/{category}/{id}-{slug}.md`. - `docs/requirements.md` — context for resolving spec terms (read-only). - `.scrum/sprint.json.id` — current sprint id, used in output paths. - Project source code + existing test suites. ## Outputs - `.scrum/integration-tests/<sprint-id>/test-cases.md` — the test-case matrix plus a spec ⇄ case traceability table (see [references/test-case-design.md](references/test-case-design.md)). - `tests/integration/**` — API integration tests in the project's test language, committed to the target project (persistent asset). - `tests/e2e/**` — Playwright UI tests, committed to the target project (persistent asset). - `tests/stubs/**` — external-interface stubs, committed to the target project. See [references/stub-construction.md](references/stub-construction.md). - `.scrum/test-results.json` — TestCategories appended via `.scrum/scripts/record-test-result.sh` (`integration_api` / `integration_ui` / `design_coverage` / `manual_probe`); `overall_status` recomputed by the wrapper. - Defect PBIs in `.scrum/backlog.json` when the quality gate fails. - A completion report to t