Files
crank/_bmad-output/test-artifacts/test-design-progress-epic-7.md
T

5.1 KiB
Raw Blame History

runScope, runKey, workflowStatus, totalSteps, stepsCompleted, lastStep, nextStep, inputDocuments, lastSaved
runScope runKey workflowStatus totalSteps stepsCompleted lastStep nextStep inputDocuments lastSaved
epic-level epic-7 completed 5
step-01-detect-mode
step-02-load-context
step-03-risk-and-testability
step-04-coverage-plan
step-05-generate-output
step-05-generate-output
_bmad-output/planning-artifacts/epics.md
_bmad-output/test-artifacts/test-design-architecture.md
_bmad-output/test-artifacts/test-design-qa.md
_bmad-output/planning-artifacts/prds/prd-crank-2026-08-03/prd.md
_bmad-output/planning-artifacts/architecture/architecture-crank-2026-08-03/ARCHITECTURE-SPINE.md
_bmad/tea/config.yaml
2026-09-13

Epic 7 test design progress

Output: test-design-epic-7.md. Completed 2026-09-13. Story/requirement/AC-count coverage, source references, risk scores and format validated. Template adapted to existing-project inventory: counts are scenario seeds, estimates are provisional QA deltas, no synthetic code-coverage or execution claim. Native loop ATDD is post-dev; pre-implementation customization is a separate pending approval, not executed by this design run.

Coverage decisions

9 story families, two independently assertable scenario seeds per family (A positive contract; B rejection/fault). The offline-upgrade AC moves from 7.5 to 7.9: bundle install/trust remains 5 groups in 7.5 and upgrade/rollback continuity becomes 8 groups in 7.9. All owning-story Given/When/Then groups remain required ATDD input; these are not a claim of exhaustive implemented test cases.

Scope: FR-41–FR-45; system families CP-25..27. Lowest effective level assigned per family. P0 security/data integrity with no workaround; P1 user/core flow. No speculative mandatory P2/P3 additions.

Source reuse: crates/crank-config/tests/{contract,generation,redaction}.rs; crates/crank-registry/tests/integration/migrations.rs and migrations/; apps/admin-api/tests/migration_command.rs; apps/admin-api/tests/config_startup.rs; scripts/restore-community.sh; scripts/authenticated-product-smoke.py; .gitea/workflows/ci.yml.

Gaps: Config/migration/auth foundations and Compose authenticated smoke exist. Restore script presence is not three qualified PITR restores. Complete offline signed bundle, role isolation with future worker/runner and full N/N-1 online/offline matrix need evidence. Prior deployment failures require regression fixtures for legacy fingerprint, missing core, external PG topology and failed migrate diagnostics, not permission to reset databases.

NFR: Each of3independent restores RPO≤5m/RTO≤30m with real MCP probe; drain≤30s and eligible Task recovery≤60s. Production sizing retains≥30% measured headroom. Zero known Critical/High, zero unapproved egress. Trust material/reference-host allocation and exact image digests are execution prerequisites, never generated secrets in docs.

Fixtures: Disposable fresh host/network namespaces; PG16 current/N-1/legacy snapshots; checksummed artifacts/WAL plus out-of-band test keys; fault checkpoints; offline registry-less image archive; default-deny egress capture; fresh scanner DB pinned in report.

Execution: PR functional tests, nightly bounded expensive/fault work, weekly calibrated qualifications; scheduled tiers are planned, not configured. Mandatory story ACs still must pass before acceptance, regardless of tier. 72h/30day release windows only in Epic8. QA effort assumption with prerequisite implementation ready: P0 48–96h; P1 16–32h; optional P2 0–8h/P3 0–4h; total 64–140h (~2–4 contributor-weeks). Not a backlog of compulsory new tests; refine against existing-test reuse during ATDD.

Risks and NFR planning

Risk Category Failure P I Score System risk Mitigation / owner / deadline
E7-R1 DATA Schema/artifact/key mismatch destroys recovery 2 3 6 R-008 Manifest + N/N-1 + three real restores; SRE, 7.8–7.9
E7-R2 SEC Unsafe defaults/proxy/privileges expose installation 2 3 6 R-007 Fresh-host negative exposure tests; Security, 7.4/7.6
E7-R3 SEC Offline bundle untrusted or phones home 2 3 6 R-014 Offline signature/tamper/egress tests; Release, 7.5

Scores describe inherent risk, not observed failures or a release verdict. Security/reliability/performance thresholds inherit the system design and owning story ACs; missing environment/measurement evidence remains explicit, never inferred PASS.

Context: Rust/PostgreSQL + browser JavaScript fullstack. Existing test source inventory at main 083974c; f8ee7c9 candidate is separate. Browser CLI absent; no live exploration, no fabricated evidence. Playwright/Pact utility flags are intentions only: packages absent; no library migration or Pact scaffolding in this planning scope. Required risk, probability/impact, test levels/priorities and NFR knowledge loaded; concrete source reuse and gaps appear in the epic plan.

Explicit batch request, independent epic scope. Requirements and acceptance criteria: planning-artifacts/epics.md, Epic 7. System designs already updated; no product implementation or test execution authorized by this planning run.