From 81c2776f7508e896bf0941964cd3c13023a7fbfd Mon Sep 17 00:00:00 2001 From: Murat Ozcan Date: Mon, 29 Sep 2025 13:52:41 -0500 Subject: [PATCH] added examples per level --- src/modules/bmm/testarch/README.md | 63 +++++++++++++++++++----------- 1 file changed, 41 insertions(+), 22 deletions(-) diff --git a/src/modules/bmm/testarch/README.md b/src/modules/bmm/testarch/README.md index 033d3d70..17003412 100644 --- a/src/modules/bmm/testarch/README.md +++ b/src/modules/bmm/testarch/README.md @@ -30,7 +30,7 @@ last-redoc-date: 2025-09-30 | Phase | Test Architect | Dev / Team | Outputs | | ------------------ | ------------------------------------------------------------------------- | -------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------- | | Setup | - | Analyst `*product-brief`, PM `*plan-project`, Architect `*solution-architecture` | `{output_folder}/product-brief*.md`, `PRD.md`, `epics.md`, `solution-architecture.md` | -| Pre-Implementation | Run `*framework` (if harness missing) and `*test-design` | Review risk/design guidance, align backlog | Test scaffold, risk memo, test design strategy | +| Pre-Implementation | Run `*framework` (if harness missing), `*ci`, and `*test-design` | Review risk/design/CI guidance, align backlog | Test scaffold, CI pipeline, risk & coverage strategy | | Story Prep | - | Scrum Master `*create-story`, `*story-context` | Story markdown + context XML | | Implementation | (Optional) Trigger `*atdd` before dev to supply failing tests + checklist | Implement story guided by ATDD checklist | Failing acceptance tests + implementation checklist | | Post-Dev | Execute `*automate`, re-run `*trace` | Address recommendations, update code/tests | Regression specs, refreshed coverage matrix | @@ -40,12 +40,23 @@ last-redoc-date: 2025-09-30 Execution Notes - Run `*framework` only once per repo or when modern harness support is missing. -- `*test-design` handles risk scoring, mitigations, and scenario planning in one pass. +- `*framework` followed by `*ci` establishes install + pipeline; `*test-design` then handles risk scoring, mitigations, and scenario planning in one pass. - Use `*atdd` before coding when the team can adopt ATDD; share its checklist with the dev agent. - Post-implementation, keep `*trace` current, expand coverage with `*automate`, and finish with `*gate`. +
+Worked Example – “Nova CRM” Greenfield Feature + +1. **Planning:** Analyst runs `*product-brief`; PM executes `*plan-project` to produce PRD and epics; Architect completes `*solution-architecture` for the new module. +2. **Setup:** TEA checks harness via `*framework`, configures `*ci`, and runs `*test-design` to capture risk/coverage plans. +3. **Story Prep:** Scrum Master generates the story via `*create-story`; PO validates using `*assess-project-ready`. +4. **Implementation:** TEA optionally runs `*atdd`; Dev implements with guidance from failing tests and the plan. +5. **Post-Dev & Release:** TEA runs `*automate`, re-runs `*trace`, and finishes with `*gate` to document the decision. + +
+ ### Brownfield Feature Enhancement (Level 2–3) | Phase | Test Architect | Dev / Team | Outputs | @@ -61,14 +72,27 @@ last-redoc-date: 2025-09-30
Execution Notes -- Lead with `*trace` so remediation plans target true coverage gaps. +- Lead with `*trace` so remediation plans target true coverage gaps. Ensure `*framework` and `*ci` are in place early in the engagement; if the brownfield lacks them, run those setup steps immediately after refreshing context. - `*test-design` should highlight regression hotspots, mitigations, and P0 scenarios. - Use `*atdd` when stories benefit from ATDD; otherwise proceed to implementation and rely on post-dev automation. -- After development, expand coverage with `*automate`, re-run `*trace`, and close with `*gate` (include `*nfr-assess` when infrastructure/perf changed). +- After development, expand coverage with `*automate`, re-run `*trace`, and close with `*gate`. Run `*nfr-assess` now if non-functional risks weren't addressed earlier. - Product Owner `*assess-project-ready` confirms the team has artifacts before handoff or release.
+
+Worked Example – “Atlas Payments” Brownfield Story + +1. **Context Refresh:** Analyst reruns `*product-brief`; PM executes `*plan-project` to update PRD, analysis, and `epics.md`; Architect triggers `*solution-architecture` capturing legacy payment flows. +2. **Baseline Coverage:** TEA executes `*trace` to record current coverage in `docs/qa/assessments/atlas-payment-trace.md`. +3. **Risk & Design:** `*test-design` flags settlement edge cases, plans mitigations, and allocates new API/E2E scenarios with P0 priorities. +4. **Story Prep:** Scrum Master generates `stories/story-1.1.md` via `*create-story`, automatically pulling updated context. +5. **ATDD First:** TEA runs `*atdd`, producing failing Playwright specs under `tests/e2e/payments/` plus an implementation checklist. +6. **Implementation:** Dev pairs with the checklist/tests to deliver the story. +7. **Post-Implementation:** TEA applies `*automate`, re-runs `*trace`, performs `*nfr-assess` to validate SLAs, and closes with `*gate` marking PASS with follow-ups. + +
+ ### Enterprise / Compliance Program (Level 4) | Phase | Test Architect | Dev / Team | Outputs | @@ -84,7 +108,18 @@ last-redoc-date: 2025-09-30 - Use `*atdd` for every story when feasible so acceptance tests lead implementation in regulated environments. - `*ci` scaffolds selective testing scripts, burn-in jobs, caching, and notifications for long-running suites. -- Prior to release, rerun coverage (`*trace`, `*automate`) and formalize the decision in `*gate`; store everything for audits. +- Prior to release, rerun coverage (`*trace`, `*automate`) and formalize the decision in `*gate`; store everything for audits. Call `*nfr-assess` here if compliance/performance requirements weren't captured during planning. + + + +
+Worked Example – “Helios Ledger” Enterprise Release + +1. **Strategic Planning:** Analyst/PM/Architect complete PRD, epics, and architecture using the standard workflows. +2. **Quality Planning:** TEA runs `*framework`, `*test-design`, and `*nfr-assess` to establish mitigations, coverage, and NFR targets. +3. **Pipeline Setup:** TEA configures CI via `*ci` with selective execution scripts. +4. **Execution:** For each story, TEA enforces `*atdd`, `*automate`, and `*trace`; Dev teams iterate on the findings. +5. **Release:** TEA re-checks coverage and logs the final gate decision via `*gate`, archiving artifacts for compliance.
@@ -111,26 +146,10 @@ last-redoc-date: 2025-09-30 -## Engagement Playbooks - -- **Greenfield Launch:** Follow the greenfield cheat sheet end-to-end—share planning artifacts up front and finish with the release row (`*gate`). -- **Brownfield Enhancement:** Use the brownfield table; baseline with `*trace`, plan remediation, and complete the release row (`*gate`, plus `*nfr-assess` when needed). -- **Enterprise / Compliance:** Add `*ci` early, enforce `*atdd`, and rely on the release row for audit-ready outputs (`*gate`). - -## Worked Example – “Atlas Payments” Brownfield Story - -1. **Context Refresh:** Analyst reruns `*product-brief`; PM executes `*plan-project` to update PRD, analysis, and `epics.md`; Architect triggers `*solution-architecture` capturing legacy payment flows. -2. **Baseline Coverage:** TEA executes `*trace` to record current coverage in `docs/qa/assessments/atlas-payment-trace.md`. -3. **Risk & Design:** `*test-design` flags settlement edge cases, plans mitigations, and allocates new API/E2E scenarios with P0 priorities. -4. **Story Prep:** Scrum Master generates `stories/story-1.1.md` via `*create-story`, automatically pulling updated context. -5. **ATDD First:** TEA runs `*atdd`, producing failing Playwright specs under `tests/e2e/payments/` plus an implementation checklist. -6. **Post-Implementation:** TEA applies `*automate`, re-runs `*trace`, performs `*nfr-assess` to validate SLAs, and closes with `*gate` marking PASS with follow-ups. - ## Appendix -- **Legacy Command Decomposition:** The historical `*review` flow is retired; coverage now handled by `*trace`, deep analysis by `*test-design`/`*nfr-assess`, and gating by `*gate`. - **Supporting Knowledge:** - `tea-knowledge.md` – Murat’s testing philosophy, heuristics, and risk scales. - `test-levels-framework.md` – Decision matrix for unit/integration/E2E selection. - `test-priorities-matrix.md` – Priority (P0–P3) criteria and target coverage percentages. -- **Visual Aids:** Coordinate with module maintainers if a flowchart or diagram should accompany these cheat sheets for downstream docs. + s