peaks-cli 1.3.8 → 1.4.0

package/skills/peaks-qa/references/test-case-generation.md

@@ -0,0 +1,27 @@
+# Mandatory test-case generation (QA)
+
+> Body of `## Mandatory test-case generation` + `## Test Case: <title>` template. QA must generate test cases, not merely inspect existing ones. Every QA invocation that validates code changes must produce a test-case artifact at `.peaks/_runtime/<sessionId>/qa/test-cases/<request-id>.md`.
+
+**Minimum test-case categories:**
+
+1. **Unit test cases** — verify that RD's unit tests cover: happy path, edge cases (null/undefined/empty), error states, boundary values, and async behavior for each changed function/component/hook
+2. **Integration test cases** — API contract verification, data flow through changed components, mock alignment with real API shapes
+3. **UI regression test cases** (frontend only) — page load, component render states (loading, empty, error, populated), modal open/close, form submit/validation, table sort/filter/pagination, navigation flow, keyboard accessibility
+
+**Test-case format:**
+
+```markdown
+## Test Case: <title>
+- **Category:** unit | integration | ui-regression
+- **Target:** <file-or-route>
+- **Acceptance:** A1, A2  (comma-separated IDs from PRD `## Acceptance criteria`; see "Acceptance linkage" below)
+- **Preconditions:** <state-before>
+- **Steps:** 1. ... 2. ...
+- **Expected result:** <what-should-happen>
+- **Status:** pass | fail | blocked | skipped
+- **Evidence:** <link-or-observation>
+```
+
+**Acceptance linkage (MANDATORY)** — every test case MUST have an `**Acceptance:**` field that references one or more acceptance items from the PRD by their position-based IDs (A1 = first bullet, A2 = second, …). The `peaks scan acceptance-coverage --rid <rid> --project <repo>` command parses both the PRD and this file, builds the coverage map, and fails the QA `verdict-issued` gate if any acceptance item has zero linked test cases. Test cases that genuinely have no acceptance owner (e.g. defense-in-depth regressions) should still include `- **Acceptance:** —` and explain in the **Evidence** field; the coverage report flags these as `unlinkedTestCases` for review without auto-blocking.
+
+**Test-case execution**: Run the project's test command and record results against each generated test case. If the project uses Jest, run `npx jest --coverage` and link the coverage report. If the project uses Vitest, run `npx vitest run --changed --coverage` by default; use the full suite `npx vitest run --coverage` only when the slice warrants a deeper regression check. Record the coverage percentage for changed files in the test report.

package/skills/peaks-qa/references/test-report-output.md

@@ -0,0 +1,14 @@
+# Mandatory test-report output (QA)
+
+> Body of `## Mandatory test-report output`. Every QA invocation must produce a test-report artifact at `.peaks/_runtime/<sessionId>/qa/test-reports/<request-id>.md`. This is separate from both the test-case file and the request artifact — do not merge.
+
+**Minimum test-report sections:**
+
+1. **Summary** — pass/fail count, coverage %, verdict (pass / return-to-rd / blocked)
+2. **Test execution results** — number of test cases executed, passed, failed, skipped
+3. **Coverage evidence** — changed-files coverage %, overall project coverage %, link to coverage report
+4. **Browser validation results** (frontend only) — pages validated, screenshots path, console errors found, network errors found
+5. **Security findings** — issues found, severity, resolution status
+6. **Performance findings** — baseline vs after numbers (build size, Lighthouse, etc. as applicable)
+7. **Residual risks** — known issues not fixed, why, mitigation
+8. **Red-line boundary check** — pass/fail against the approved scope