workflows indicate web_bundle file inclusions

2025-12-29 16:14:59 +00:00 · 2025-09-29 20:19:14 -05:00
parent 023edd1b7b
commit 9934224230
147 changed files with 740 additions and 478 deletions
--- a/src/modules/bmm/testarch/README.md
+++ b/src/modules/bmm/testarch/README.md
@@ -6,11 +6,11 @@ last-redoc-date: 2025-09-30

 ## Overview

- **Persona:** Murat, Master Test Architect & Quality Advisor focused on risk-based testing, fixture architecture, ATDD, and CI/CD governance.
+- **Persona:** Murat, Master Test Architect and Quality Advisor focused on risk-based testing, fixture architecture, ATDD, and CI/CD governance.
 - **Mission:** Deliver actionable quality strategies, automation coverage, and gate decisions that scale with project level and compliance demands.
 - **Use When:** Project level ≥2, integration risk is non-trivial, brownfield regression risk exists, or compliance/NFR evidence is required.

-## Prerequisites & Setup
+## Prerequisites and Setup

 1. Run the core planning workflows first:
   - Analyst `*product-brief`
@@ -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), `*ci`, and `*test-design`          | Review risk/design/CI guidance, align backlog                                    | Test scaffold, CI pipeline, risk & coverage strategy                                  |
+| Pre-Implementation | Run `*framework` (if harness missing), `*ci`, and `*test-design`          | Review risk/design/CI guidance, align backlog                                    | Test scaffold, CI pipeline, risk and 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                                           |
@@ -53,7 +53,7 @@ last-redoc-date: 2025-09-30
 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.
+5. **Post-Dev and Release:** TEA runs `*automate`, re-runs `*trace`, and finishes with `*gate` to document the decision.

 </details>

@@ -85,7 +85,7 @@ last-redoc-date: 2025-09-30

 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.
+3. **Risk and 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.
@@ -137,7 +137,7 @@ last-redoc-date: 2025-09-30
 | `*gate`        | `testarch/gate.md`               | Gate YAML + summary (PASS/CONCERNS/FAIL/WAIVED)                      | Deterministic decision rules + rationale         |

 <details>
-<summary>Command Guidance & Context Loading</summary>
+<summary>Command Guidance and Context Loading</summary>

 - Each task reads one row from `tea-commands.csv` via `command_key`, expanding pipe-delimited (`|`) values into checklists.
 - Keep CSV rows lightweight; place in-depth heuristics in `tea-knowledge.md` and reference via `knowledge_tags`.
--- a/src/modules/bmm/testarch/tea-knowledge.md
+++ b/src/modules/bmm/testarch/tea-knowledge.md
@@ -15,7 +15,7 @@ This brief distills Murat Ozcan's testing philosophy used by the Test Architect
 - Setup via API, assert via UI. Keep tests user-centric while priming state through fast interfaces.
 - One test = one concern. Explicit assertions live in the test body, not buried in helpers.

-## Patterns & Heuristics
+## Patterns and Heuristics

 - Selector order: `data-cy` / `data-testid` -> ARIA -> text. Avoid brittle CSS, IDs, or index based locators.
 - Network boundary is the mock boundary. Stub at the edge, never mid-service unless risk demands.
@@ -46,7 +46,7 @@ This brief distills Murat Ozcan's testing philosophy used by the Test Architect
  ```
 - Visual debugging: keep component/test runner UIs available (Playwright trace viewer, Cypress runner) to accelerate feedback.

-## Risk & Coverage
+## Risk and Coverage

 - Risk score = probability (1-3) × impact (1-3). Score 9 => gate FAIL, ≥6 => CONCERNS. Most stories have 0-1 high risks.
 - Test level ratio: heavy unit/component coverage, but always include E2E for critical journeys and integration seams.
@@ -60,7 +60,7 @@ This brief distills Murat Ozcan's testing philosophy used by the Test Architect
 - **Media**: screenshot only-on-failure, video retain-on-failure
 - **Language Matching**: Tests should match source code language (JS/TS frontend -> JS/TS tests)

-## Automation & CI
+## Automation and CI

 - Prefer Playwright for multi-language teams, worker parallelism, rich debugging; Cypress suits smaller DX-first repos or component-heavy spikes.
 - **Framework Selection**: Large repo + performance = Playwright, Small repo + DX = Cypress
@@ -71,7 +71,7 @@ This brief distills Murat Ozcan's testing philosophy used by the Test Architect
 - Burn-in testing: run new or changed specs multiple times (e.g., 3-10x) to flush flakes before they land in main.
 - Keep helper scripts handy (`scripts/test-changed.sh`, `scripts/burn-in-changed.sh`) so CI and local workflows stay in sync.

-## Project Structure & Config
+## Project Structure and Config

 - **Directory structure**:
  ```
@@ -93,7 +93,7 @@ This brief distills Murat Ozcan's testing philosophy used by the Test Architect
  export default configs[process.env.TEST_ENV || 'local'];
  ```

-## Test Hygiene & Independence
+## Test Hygiene and Independence

 - Tests must be independent and stateless; never rely on execution order.
 - Cleanup all data created during tests (afterEach or API cleanup).
@@ -127,7 +127,7 @@ This brief distills Murat Ozcan's testing philosophy used by the Test Architect
  "test:component": "cypress run --component",
  "test:contract": "jest --testMatch='**/pact/*.spec.ts'",
  "test:debug": "playwright test --headed",
-  "test:ci": "npm run test:unit && npm run test:e2e",
+  "test:ci": "npm run test:unit andand npm run test:e2e",
  "contract:publish": "pact-broker publish"
  ```

@@ -138,7 +138,7 @@ This brief distills Murat Ozcan's testing philosophy used by the Test Architect
 - Structure: `pact/` directory at root, `pact/config.ts` for broker settings.
 - Reference repos: pact-js-example-consumer, pact-js-example-provider, pact-js-example-react-consumer.

-## Online Resources & Examples
+## Online Resources and Examples

 - Fixture architecture: https://github.com/muratkeremozcan/cy-vs-pw-murats-version
 - Playwright patterns: https://github.com/muratkeremozcan/pw-book
@@ -156,7 +156,7 @@ This brief distills Murat Ozcan's testing philosophy used by the Test Architect
 - BUS: Business or user harm, revenue-impacting failures, compliance gaps.
 - OPS: Deployment, infrastructure, or observability gaps that block releases.

-## Probability & Impact Scale
+## Probability and Impact Scale

 - Probability 1 = Unlikely (standard implementation, low risk).
 - Probability 2 = Possible (edge cases, needs attention).
--- a/src/modules/bmm/testarch/test-design.md
+++ b/src/modules/bmm/testarch/test-design.md
@@ -1,9 +1,9 @@
 <!-- Powered by BMAD-CORE™ -->

-# Risk & Test Design v3.0 (Slim)
+# Risk and Test Design v3.0 (Slim)

 ```xml
-<task id="bmad/bmm/testarch/test-design" name="Risk & Test Design">
+<task id="bmad/bmm/testarch/test-design" name="Risk andamp; Test Design">
  <llm critical="true">
    <i>Set command_key="*test-design"</i>
    <i>Load {project-root}/bmad/bmm/testarch/tea-commands.csv and parse the matching row</i>