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

5.5 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-2 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 2 test design progress

Output: test-design-epic-2.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

15 story families, two independently assertable scenario seeds per family (A positive contract; B rejection/fault). Approved numbering splits former 2.10 into 2.10 API (former groups 1–10, 12) and 2.11 UI (former 11 plus UI perspectives of 3 and 5); old 2.11–2.14 become 2.12–2.15. All owning-story Given/When/Then groups remain required ATDD input; these are not a claim of exhaustive implemented test cases.

Scope: FR-7–FR-12; system families CP-05..07. 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-artifacts/tests/{artifact_store,artifact_store_io,reconciliation}.rs; crates/crank-registry/tests/integration/{artifact_sources,artifact_reconciliation}.rs; apps/admin-api/tests/integration/openapi_source/; crates/crank-import/tests/{preview,coverage,normalization_details,reference_resolution}.rs; apps/admin-api/tests/integration/openapi_import/; apps/ui/tests/e2e/operations.spec.js.

Gaps: 2.1–2.6 source/metadata/reconciliation/preview and 2.7–2.8 have reusable source tests, not fresh acceptance evidence. 2.9 tests exist only at candidate f8ee7c9, not main 083974c; rerun after integration. Security-scheme API/UI mapping, full partial/re-import policy matrix, ≥50-spec corpus and OpenAPI onboarding still need story-level deltas. Two candidate review deferrals (reverse URL placeholder validation and object/array default projection) remain explicit triage inputs, not automatically accepted or added to every story.

NFR: Zero silent semantic loss; ≥50 versioned specs and ≥95% actionable Draft operations (2.14). Source size/depth/time/scan budgets come from the typed contract; test min/max/over-limit, do not invent limits. No secrets outside allowed encrypted authority. Test artifact retention under reference/cleanup contention.

Fixtures: Immutable hostile/valid YAML/JSON corpus with expected IR and wire outcomes; local allowlisted HTTP/DNS fixtures; isolated temp roots; real PostgreSQL schemas; reproducible crash checkpoints. File-size fault tests must retain pipe/PTY stdout rather than a regular-file redirect.

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 40–80h; P1 20–40h; optional P2 0–8h/P3 0–4h; total 60–132h (~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
E2-R1 DATA Silent HTTP/schema loss in supported imports 3 3 9 R-002 Wire oracle + IR/ref/plan golden tests; Import owner, before 2.14
E2-R2 SEC Hostile files/refs escape scope, leak secrets or exhaust resources 3 3 9 R-004 Bounded parser/network/storage canaries; Security + Import, each source story
E2-R3 DATA GC/re-import races lose pinned artifacts or overwrite revisions 2 3 6 R-008 Real PG + filesystem fault interleavings; Registry, before 2.13
E2-R4 TECH Flaky preview UI/evidence masks failed import 2 2 4 R-012 Stale-response tests + strict evidence; UI/QA, 2.6/2.15

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 2. System designs already updated; no product implementation or test execution authorized by this planning run.