bmad-method-test-architecture-enterprise 1.2.2 → 1.2.3

package/README.md

@@ -68,17 +68,17 @@ npx bmad-method install
 
 ## Workflows
 
-| Trigger | Command                      | Purpose                                       |
-| ------- | ---------------------------- | --------------------------------------------- |
-| TMT     | `/bmad:tea:teach-me-testing` | Teach Me Testing (TEA Academy)                |
-| TF      | `/bmad:tea:framework`        | Scaffold Playwright/Cypress test framework    |
-| CI      | `/bmad:tea:ci`               | Set up CI/CD quality pipeline                 |
-| TD      | `/bmad:tea:test-design`      | System-level or epic-level test design        |
-| AT      | `/bmad:tea:atdd`             | Generate failing acceptance tests + checklist |
-| TA      | `/bmad:tea:automate`         | Expand test automation coverage               |
-| RV      | `/bmad:tea:test-review`      | Review test quality and score                 |
-| TR      | `/bmad:tea:trace`            | Trace requirements to tests + gate decision   |
-| NR      | `/bmad:tea:nfr-assess`       | Assess non-functional requirements            |
+| Trigger | Command                      | Purpose                                                   |
+| ------- | ---------------------------- | --------------------------------------------------------- |
+| TMT     | `/bmad:tea:teach-me-testing` | Teach Me Testing (TEA Academy)                            |
+| TF      | `/bmad:tea:framework`        | Scaffold test framework (frontend, backend, or fullstack) |
+| CI      | `/bmad:tea:ci`               | Set up CI/CD quality pipeline (multi-platform)            |
+| TD      | `/bmad:tea:test-design`      | System-level or epic-level test design                    |
+| AT      | `/bmad:tea:atdd`             | Generate failing acceptance tests + checklist             |
+| TA      | `/bmad:tea:automate`         | Expand test automation coverage                           |
+| RV      | `/bmad:tea:test-review`      | Review test quality and score                             |
+| TR      | `/bmad:tea:trace`            | Trace requirements to tests + gate decision               |
+| NR      | `/bmad:tea:nfr-assess`       | Assess non-functional requirements                        |
 
 ## Configuration
 
@@ -87,7 +87,9 @@ TEA variables are defined in `src/module.yaml` and prompted during install:
 - `test_artifacts` — base output folder for test artifacts
 - `tea_use_playwright_utils` — enable Playwright Utils integration (boolean)
 - `tea_browser_automation` — browser automation mode: auto, cli, mcp, none (string)
-- `test_framework` — default framework preference (future)
+- `test_framework` — detected or configured test framework (Playwright, Cypress, Jest, Vitest, pytest, JUnit, Go test, dotnet test, RSpec)
+- `test_stack_type` — detected or configured stack type (frontend, backend, fullstack)
+- `ci_platform` — CI platform (auto, github-actions, gitlab-ci, jenkins, azure-devops, harness, circle-ci)
 - `risk_threshold` — risk cutoff for mandatory testing (future)
 - `test_design_output`, `test_review_output`, `trace_output` — subfolders under `test_artifacts`
 

package/docs/how-to/workflows/setup-ci.md

@@ -48,8 +48,10 @@ TEA will ask which platform you're using.
 
 - **GitHub Actions** (most common)
 - **GitLab CI**
+- **Jenkins** — Generates `Jenkinsfile` with parallel stages, artifact archiving, and post-failure handling
+- **Azure DevOps** — Generates `azure-pipelines.yml` with matrix strategy for sharding and Azure-specific caching
+- **Harness** — Generates `.harness/pipeline.yaml` with Kubernetes-based execution and parallel steps
 - **Circle CI**
-- **Jenkins**
 - **Other** (TEA provides generic template)
 
 **Example:**

package/docs/how-to/workflows/setup-test-framework.md

@@ -36,22 +36,31 @@ framework
 TEA will ask about:
 
 - Your tech stack (React, Node, etc.)
-- Preferred test framework (Playwright, Cypress, Jest)
-- Testing scope (E2E, integration, unit)
-- CI/CD platform (GitHub Actions, etc.)
+- Preferred test framework:
+  - **Frontend/Fullstack**: Playwright, Cypress
+  - **Backend (Node.js)**: Jest, Vitest, or Playwright (API testing via playwright-utils)
+  - **Backend (Python)**: pytest, or Playwright for Python
+  - **Backend (Java/Kotlin)**: JUnit, or Playwright for Java
+  - **Backend (Go)**: Go test
+  - **Backend (C#/.NET)**: dotnet test / xUnit, or Playwright for .NET
+  - **Backend (Ruby)**: RSpec
+- Testing scope (E2E, integration, unit, API)
+- CI/CD platform (GitHub Actions, GitLab CI, Jenkins, Azure DevOps, Harness, etc.)
 
 ### 4. Review Generated Output
 
 TEA generates:
 
-- **Test scaffold** — Directory structure and config files
-- **Sample specs** — Example tests following best practices
+- **Test scaffold** — Directory structure and config files (language-idiomatic)
+- **Sample specs** — Example tests following best practices for your framework
 - **`.env.example`** — Environment variable template
-- **`.nvmrc`** — Node version specification
+- **Version file** — `.nvmrc` (Node.js), `.python-version` (Python), `global.json` (.NET), etc.
 - **README updates** — Testing documentation
 
 ## What You Get
 
+**Frontend/Fullstack (Node.js):**
+
 ```
 tests/
 ├── e2e/
@@ -63,6 +72,20 @@ tests/
 └── README.md
 ```
 
+**Backend (Python example):**
+
+```
+tests/
+├── unit/
+│   └── test_example.py
+├── integration/
+├── api/
+├── conftest.py
+└── README.md
+```
+
+> **Note:** Playwright has official bindings for Python, Java, and .NET — making it viable for API testing across languages, not just Node.js.
+
 ## Optional: Playwright Utils Integration
 
 TEA can integrate with `@seontechnologies/playwright-utils` for advanced fixtures:

package/docs/reference/configuration.md

@@ -209,6 +209,103 @@ tea_browser_automation: 'none'
 
 ---
 
+### test_stack_type
+
+Detected or configured project stack type. Controls CI pipeline generation and framework selection.
+
+**Schema Location:** `src/module.yaml` (TEA module config)
+
+**User Config:** `_bmad/tea/config.yaml`
+
+**Type:** `string`
+
+**Default:** `"auto"`
+
+**Options:** `"auto"` | `"frontend"` | `"backend"` | `"fullstack"`
+
+**Purpose:** Determines stack-specific behavior:
+
+| Stack Type  | Behavior                                                                                                   |
+| ----------- | ---------------------------------------------------------------------------------------------------------- |
+| `auto`      | Auto-detect from project manifests (playwright.config, jest.config, etc.)                                  |
+| `frontend`  | Browser-based tests (Playwright/Cypress), browser install in CI, burn-in enabled                           |
+| `backend`   | API/unit tests (pytest, JUnit, Go test, Jest/Vitest, etc.), no browser install, burn-in skipped by default |
+| `fullstack` | Both frontend and backend tests, full CI pipeline                                                          |
+
+**Affects Workflows:**
+
+- `ci` - Stack-conditional pipeline stages (browser install, burn-in)
+- `framework` - Framework scaffold adapts to stack type
+
+**Example:**
+
+```yaml
+test_stack_type: 'fullstack'
+```
+
+---
+
+### ci_platform
+
+CI/CD platform for pipeline generation.
+
+**Schema Location:** `src/module.yaml` (TEA module config)
+
+**User Config:** `_bmad/tea/config.yaml`
+
+**Type:** `string`
+
+**Default:** `"auto"`
+
+**Options:** `"auto"` | `"github-actions"` | `"gitlab-ci"` | `"jenkins"` | `"azure-devops"` | `"harness"` | `"circle-ci"` | `"other"`
+
+**Purpose:** Controls which CI template is used for pipeline generation.
+
+When set to `"auto"`, TEA detects the platform by scanning for existing CI configuration files (`.github/workflows/`, `.gitlab-ci.yml`, `Jenkinsfile`, `azure-pipelines.yml`, `.harness/`, `.circleci/config.yml`) and falls back to inferring from the git remote.
+
+**Affects Workflows:**
+
+- `ci` - Template selection and output path
+
+**Example:**
+
+```yaml
+ci_platform: 'github-actions'
+```
+
+---
+
+### test_framework
+
+Detected or configured test framework preference.
+
+**Schema Location:** `src/module.yaml` (TEA module config)
+
+**User Config:** `_bmad/tea/config.yaml`
+
+**Type:** `string`
+
+**Default:** `"auto"`
+
+**Options:** `"auto"` | `"playwright"` | `"cypress"` | `"jest"` | `"vitest"` | `"pytest"` | `"junit"` | `"go-test"` | `"dotnet-test"` | `"rspec"` | `"other"`
+
+**Purpose:** Controls which test framework patterns TEA uses for code generation. When set to `"auto"`, TEA detects from project configuration files and manifests. Supports both frontend (Playwright, Cypress, Jest, Vitest) and backend (pytest, JUnit, Go test, dotnet test, RSpec) frameworks.
+
+**Affects Workflows:**
+
+- `framework` - Scaffold generation
+- `ci` - Test commands in pipeline
+- `atdd` - Test code generation patterns
+- `automate` - Test code generation patterns
+
+**Example:**
+
+```yaml
+test_framework: 'playwright'
+```
+
+---
+
 ## Core BMM Configuration (Inherited by TEA)
 
 TEA also uses core BMM configuration options from `_bmad/tea/config.yaml`:

package/docs/reference/knowledge-base.md

@@ -41,9 +41,9 @@ User runs a TEA workflow (e.g., `test-design`)
 TEA reads `src/testarch/tea-index.csv`:
 
 ```csv
-id,name,description,tags,fragment_file
-test-quality,Test Quality,Execution limits and isolation rules,"quality,standards",knowledge/test-quality.md
-risk-governance,Risk Governance,Risk scoring and gate decisions,"risk,governance",knowledge/risk-governance.md
+id,name,description,tags,tier,fragment_file
+test-quality,Test Quality,Execution limits and isolation rules,"quality,standards",core,knowledge/test-quality.md
+risk-governance,Risk Governance,Risk scoring and gate decisions,"risk,governance",core,knowledge/risk-governance.md
 ```
 
 ### 3. Dynamic Loading
@@ -217,9 +217,9 @@ Patterns for using `@seontechnologies/playwright-utils` package (9 utilities).
 **Structure:**
 
 ```csv
-id,name,description,tags,fragment_file
-test-quality,Test Quality,Execution limits and isolation rules,"quality,standards",knowledge/test-quality.md
-risk-governance,Risk Governance,Risk scoring and gate decisions,"risk,governance",knowledge/risk-governance.md
+id,name,description,tags,tier,fragment_file
+test-quality,Test Quality,Execution limits and isolation rules,"quality,standards",core,knowledge/test-quality.md
+risk-governance,Risk Governance,Risk scoring and gate decisions,"risk,governance",core,knowledge/risk-governance.md
 ```
 
 **Columns:**
@@ -228,8 +228,17 @@ risk-governance,Risk Governance,Risk scoring and gate decisions,"risk,governance
 - `name` - Human-readable fragment name
 - `description` - What the fragment covers
 - `tags` - Searchable tags (comma-separated)
+- `tier` - Loading priority (`core` = always loaded for matching workflow, `extended` = loaded on demand, `specialized` = loaded only when the specific use case matches)
 - `fragment_file` - Relative path to fragment markdown file
 
+**Loading Profiles:**
+
+Fragments are loaded based on workflow needs and tier priority:
+
+- **Core tier**: Automatically loaded when a workflow starts (e.g., `test-quality.md` for `test-review`)
+- **Extended tier**: Loaded when the workflow context requires them (e.g., `auth-session.md` when tests involve authentication)
+- **Specialized tier**: Only loaded when the specific use case matches (e.g., contract-testing for microservices, email-auth for email flows)
+
 **Fragment Location:** `src/testarch/knowledge/` (all 35 fragments in single directory)
 
 **Manifest:** `src/testarch/tea-index.csv`

package/package.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/package.json",
   "name": "bmad-method-test-architecture-enterprise",
-  "version": "1.2.2",
+  "version": "1.2.3",
   "description": "Master Test Architect for quality strategy, test automation, and release gates",
   "keywords": [
     "bmad",

package/release_notes.md

@@ -1,10 +1,12 @@
-## 🚀 What's New in v1.2.2
+## 🚀 What's New in v1.2.3
 
 ### 🐛 Bug Fixes
-- fix: issue 29
+- fix: issues 32 through 37
 
 ### 📦 Other Changes
-- Merge pull request #31 from bmad-code-org/fix/issue-29
+- addressed PR comments
+- addressed PR comments2
+- Merge pull request #38 from bmad-code-org/fix/issues-32-33-34-35-35-36-37
 
 
 ## 📦 Installation
@@ -14,4 +16,4 @@ npx bmad-method install
 # Select "Test Architect" from module menu
 ```
 
-**Full Changelog**: https://github.com/bmad-code-org/bmad-method-test-architecture-enterprise/compare/v1.2.1...v1.2.2
+**Full Changelog**: https://github.com/bmad-code-org/bmad-method-test-architecture-enterprise/compare/v1.2.2...v1.2.3

package/src/agents/tea.agent.yaml

@@ -12,7 +12,7 @@ agent:
 
   persona:
     role: Master Test Architect
-    identity: Test architect specializing in risk-based testing, fixture architecture, ATDD, API testing, backend services, UI automation, CI/CD governance, and scalable quality gates. Equally proficient in pure API/service-layer testing as in browser-based E2E testing.
+    identity: Test architect specializing in risk-based testing, fixture architecture, ATDD, API testing, backend services, UI automation, CI/CD governance, and scalable quality gates. Equally proficient in pure API/service-layer testing (pytest, JUnit, Go test, xUnit, RSpec) as in browser-based E2E testing (Playwright, Cypress). Supports GitHub Actions, GitLab CI, Jenkins, Azure DevOps, and Harness CI platforms.
     communication_style: "Blends data with gut instinct. 'Strong opinions, weakly held' is their mantra. Speaks in risk calculations and impact assessments."
     principles: |
       - Risk-based testing - depth scales with impact
@@ -27,7 +27,7 @@ agent:
   critical_actions:
     - "Consult {project-root}/_bmad/tea/testarch/tea-index.csv to select knowledge fragments under knowledge/ and load only the files needed for the current task"
     - "Load the referenced fragment(s) from {project-root}/_bmad/tea/testarch/knowledge/ before giving recommendations"
-    - "Cross-check recommendations with the current official Playwright, Cypress, Pact, and CI platform documentation"
+    - "Cross-check recommendations with the current official Playwright, Cypress, pytest, JUnit, Go test, Pact, and CI platform documentation"
 
   menu:
     - trigger: TMT or fuzzy match on teach-me-testing

package/src/module.yaml

@@ -13,7 +13,7 @@ default_selected: false
 ## project_root
 
 # TEA-specific configuration variables
-# IMPORTANT: Only tea_use_playwright_utils and tea_browser_automation are ACTIVELY USED in workflows
+# IMPORTANT: tea_use_playwright_utils, tea_browser_automation, test_stack_type, ci_platform, and test_framework are ACTIVELY USED in workflows
 # Other variables are FUTURE placeholders for Phase 10 enhancements
 
 test_artifacts:
@@ -50,16 +50,70 @@ tea_browser_automation:
     - value: "none"
       label: "None - No live browser interaction"
 
-# ⏭️ FUTURE - Test framework selection (not currently wired into workflows, marked for Phase 10)
+# ✅ ACTIVELY USED - Stack type detection for multi-framework support
+test_stack_type:
+  prompt: "What type of project is this?"
+  default: "auto"
+  result: "{value}"
+  single-select:
+    - value: "auto"
+      label: "Auto-detect from project files (Recommended)"
+    - value: "frontend"
+      label: "Frontend (Node.js, React, Vue, Angular)"
+    - value: "backend"
+      label: "Backend (Python, Java, Go, .NET, Rust)"
+    - value: "fullstack"
+      label: "Full-stack (both frontend and backend)"
+
+# ✅ ACTIVELY USED - CI/CD platform detection
+ci_platform:
+  prompt: "Which CI/CD platform do you use?"
+  default: "auto"
+  result: "{value}"
+  single-select:
+    - value: "auto"
+      label: "Auto-detect from repository (Recommended)"
+    - value: "github-actions"
+      label: "GitHub Actions"
+    - value: "gitlab-ci"
+      label: "GitLab CI"
+    - value: "jenkins"
+      label: "Jenkins"
+    - value: "azure-devops"
+      label: "Azure DevOps Pipelines"
+    - value: "harness"
+      label: "Harness CI"
+    - value: "circle-ci"
+      label: "CircleCI"
+    - value: "other"
+      label: "Other/Custom"
+
+# ✅ ACTIVELY USED - Test framework selection for multi-stack support
 test_framework:
   prompt: "Which test framework are you using?"
-  default: "playwright"
+  default: "auto"
   result: "{value}"
   single-select:
+    - value: "auto"
+      label: "Auto-detect from project files (Recommended)"
     - value: "playwright"
-      label: "Playwright (Recommended)"
+      label: "Playwright (JavaScript/TypeScript)"
     - value: "cypress"
-      label: "Cypress"
+      label: "Cypress (JavaScript/TypeScript)"
+    - value: "jest"
+      label: "Jest (JavaScript/TypeScript)"
+    - value: "vitest"
+      label: "Vitest (JavaScript/TypeScript)"
+    - value: "pytest"
+      label: "pytest (Python)"
+    - value: "junit"
+      label: "JUnit (Java/Kotlin)"
+    - value: "go-test"
+      label: "Go test (Go)"
+    - value: "dotnet-test"
+      label: "dotnet test (C#/.NET)"
+    - value: "rspec"
+      label: "RSpec (Ruby)"
     - value: "other"
       label: "Other/Custom"
 
@@ -96,6 +150,25 @@ trace_output:
   result: "{test_artifacts}/{value}"
 
 post-install-notes:
+  test_stack_type:
+    auto: |
+      Stack Auto-Detection:
+        TEA will detect your project type from manifest files:
+        - Frontend: package.json with react/vue/angular, playwright.config.*, vite.config.*
+        - Backend: pyproject.toml, pom.xml, go.mod, *.csproj, Gemfile, Cargo.toml
+        - Full-stack: both frontend and backend indicators present
+        Existing installations without test_stack_type default to "auto" (detects frontend).
+  ci_platform:
+    auto: |
+      CI Platform Auto-Detection:
+        TEA will detect your CI platform from repository files:
+        - GitHub Actions: .github/workflows/
+        - GitLab CI: .gitlab-ci.yml
+        - Jenkins: Jenkinsfile
+        - Azure DevOps: azure-pipelines.yml
+        - Harness: .harness/
+        - CircleCI: .circleci/config.yml
+        Existing installations without ci_platform default to "auto".
   tea_browser_automation:
     cli: |
       Playwright CLI Setup:

package/src/testarch/knowledge/adr-quality-readiness-checklist.md

@@ -328,20 +328,20 @@ Can we verify this effectively without manual toil?
 
 **Question:** Can we verify this effectively without manual toil?
 
-| Criterion                    | Status | Evidence                 | Gap/Action               |
-| ---------------------------- | ------ | ------------------------ | ------------------------ |
-| ⬜ Isolation: Mock deps      | ⚠️     | No Athena mock           | Implement mock endpoints |
-| ⬜ Headless: API-accessible  | ✅     | All MCP tools are REST   | N/A                      |
-| ⬜ State Control: Seeding    | ⚠️     | `/api/test-data` pending | Sprint 0 blocker         |
-| ⬜ Sample Requests: Examples | ⬜     | Pending schemas          | Finalize ADR Tools       |
+| Criterion                    | Status | Evidence                 | Gap/Action                 |
+| ---------------------------- | ------ | ------------------------ | -------------------------- |
+| ⬜ Isolation: Mock deps      | ⚠️     | No Athena mock           | Implement mock endpoints   |
+| ⬜ Headless: API-accessible  | ✅     | All MCP tools are REST   | N/A                        |
+| ⬜ State Control: Seeding    | ⚠️     | `/api/test-data` pending | Pre-implementation blocker |
+| ⬜ Sample Requests: Examples | ⬜     | Pending schemas          | Finalize ADR Tools         |
 
 **Overall Status:** ⚠️ CONCERNS (2/4 criteria met)
 
 **Next Actions:**
 
-- [ ] Backend: Implement Athena mock endpoints (Sprint 0)
-- [ ] Backend: Implement `/api/test-data` (Sprint 0)
-- [ ] PM: Finalize sample requests (Sprint 1)
+- [ ] Backend: Implement Athena mock endpoints (pre-implementation)
+- [ ] Backend: Implement `/api/test-data` (pre-implementation)
+- [ ] PM: Finalize sample requests (implementation phase)
 
 {Repeat for all 8 categories}
 ```

package/src/testarch/tea-index.csv

@@ -1,36 +1,36 @@
-id,name,description,tags,fragment_file
-fixture-architecture,Fixture Architecture,"Composable fixture patterns (pure function → fixture → merge) and reuse rules","fixtures,architecture,playwright,cypress",knowledge/fixture-architecture.md
-network-first,Network-First Safeguards,"Intercept-before-navigate workflow, HAR capture, deterministic waits, edge mocking","network,stability,playwright,cypress,ui",knowledge/network-first.md
-data-factories,Data Factories and API Setup,"Factories with overrides, API seeding, cleanup discipline","data,factories,setup,api,backend,seeding",knowledge/data-factories.md
-component-tdd,Component TDD Loop,"Red→green→refactor workflow, provider isolation, accessibility assertions","component-testing,tdd,ui",knowledge/component-tdd.md
-playwright-config,Playwright Config Guardrails,"Environment switching, timeout standards, artifact outputs","playwright,config,env",knowledge/playwright-config.md
-ci-burn-in,CI and Burn-In Strategy,"Staged jobs, shard orchestration, burn-in loops, artifact policy","ci,automation,flakiness",knowledge/ci-burn-in.md
-selective-testing,Selective Test Execution,"Tag/grep usage, spec filters, diff-based runs, promotion rules","risk-based,selection,strategy",knowledge/selective-testing.md
-feature-flags,Feature Flag Governance,"Enum management, targeting helpers, cleanup, release checklists","feature-flags,governance,launchdarkly",knowledge/feature-flags.md
-contract-testing,Contract Testing Essentials,"Pact publishing, provider verification, resilience coverage","contract-testing,pact,api,backend,microservices,service-contract",knowledge/contract-testing.md
-email-auth,Email Authentication Testing,"Magic link extraction, state preservation, caching, negative flows","email-authentication,security,workflow",knowledge/email-auth.md
-error-handling,Error Handling Checks,"Scoped exception handling, retry validation, telemetry logging","resilience,error-handling,stability,api,backend",knowledge/error-handling.md
-visual-debugging,Visual Debugging Toolkit,"Trace viewer usage, artifact expectations, accessibility integration","debugging,dx,tooling,ui",knowledge/visual-debugging.md
-risk-governance,Risk Governance,"Scoring matrix, category ownership, gate decision rules","risk,governance,gates",knowledge/risk-governance.md
-probability-impact,Probability and Impact Scale,"Shared definitions for scoring matrix and gate thresholds","risk,scoring,scale",knowledge/probability-impact.md
-test-quality,Test Quality Definition of Done,"Execution limits, isolation rules, green criteria","quality,definition-of-done,tests",knowledge/test-quality.md
-nfr-criteria,NFR Review Criteria,"Security, performance, reliability, maintainability status definitions","nfr,assessment,quality",knowledge/nfr-criteria.md
-test-levels,Test Levels Framework,"Guidelines for choosing unit, integration, or end-to-end coverage","testing,levels,selection,api,backend,ui",knowledge/test-levels-framework.md
-test-priorities,Test Priorities Matrix,"P0–P3 criteria, coverage targets, execution ordering","testing,prioritization,risk",knowledge/test-priorities-matrix.md
-test-healing-patterns,Test Healing Patterns,"Common failure patterns and automated fixes","healing,debugging,patterns",knowledge/test-healing-patterns.md
-selector-resilience,Selector Resilience,"Robust selector strategies and debugging techniques","selectors,locators,debugging,ui",knowledge/selector-resilience.md
-timing-debugging,Timing Debugging,"Race condition identification and deterministic wait fixes","timing,async,debugging",knowledge/timing-debugging.md
-overview,Playwright Utils Overview,"Installation, design principles, fixture patterns for API and UI testing","playwright-utils,fixtures,api,backend,ui",knowledge/overview.md
-api-request,API Request,"Typed HTTP client, schema validation, retry logic, operation-based overload for API and service testing","api,backend,service-testing,api-testing,playwright-utils,openapi,codegen,operation",knowledge/api-request.md
-network-recorder,Network Recorder,"HAR record/playback, CRUD detection for offline UI testing","network,playwright-utils,ui,har",knowledge/network-recorder.md
-auth-session,Auth Session,"Token persistence, multi-user, API and browser authentication","auth,playwright-utils,api,backend,jwt,token",knowledge/auth-session.md
-intercept-network-call,Intercept Network Call,"Network spy/stub, JSON parsing for UI tests","network,playwright-utils,ui",knowledge/intercept-network-call.md
-recurse,Recurse Polling,"Async polling for API responses, background jobs, eventual consistency","polling,playwright-utils,api,backend,async,eventual-consistency",knowledge/recurse.md
-log,Log Utility,"Report logging, structured output for API and UI tests","logging,playwright-utils,api,ui",knowledge/log.md
-file-utils,File Utilities,"CSV/XLSX/PDF/ZIP validation for API exports and UI downloads","files,playwright-utils,api,backend,ui",knowledge/file-utils.md
-burn-in,Burn-in Runner,"Smart test selection, git diff for CI optimization","ci,playwright-utils",knowledge/burn-in.md
-network-error-monitor,Network Error Monitor,"HTTP 4xx/5xx detection for UI tests","monitoring,playwright-utils,ui",knowledge/network-error-monitor.md
-fixtures-composition,Fixtures Composition,"mergeTests composition patterns for combining utilities","fixtures,playwright-utils",knowledge/fixtures-composition.md
-api-testing-patterns,API Testing Patterns,"Pure API test patterns without browser: service testing, microservices, GraphQL","api,backend,service-testing,api-testing,microservices,graphql,no-browser",knowledge/api-testing-patterns.md
-adr-quality-readiness-checklist,ADR Quality Readiness Checklist,"8-category 29-criteria framework for ADR testability and NFR assessment","nfr,testability,adr,quality,assessment,checklist",knowledge/adr-quality-readiness-checklist.md
-playwright-cli,Playwright CLI,"Token-efficient CLI for AI coding agents: element refs, sessions, snapshots, browser automation","cli,browser,agent,automation,snapshot",knowledge/playwright-cli.md
+id,name,description,tags,tier,fragment_file
+fixture-architecture,Fixture Architecture,"Composable fixture patterns (pure function → fixture → merge) and reuse rules","fixtures,architecture,playwright,cypress",core,knowledge/fixture-architecture.md
+network-first,Network-First Safeguards,"Intercept-before-navigate workflow, HAR capture, deterministic waits, edge mocking","network,stability,playwright,cypress,ui",core,knowledge/network-first.md
+data-factories,Data Factories and API Setup,"Factories with overrides, API seeding, cleanup discipline","data,factories,setup,api,backend,seeding",core,knowledge/data-factories.md
+component-tdd,Component TDD Loop,"Red→green→refactor workflow, provider isolation, accessibility assertions","component-testing,tdd,ui",extended,knowledge/component-tdd.md
+playwright-config,Playwright Config Guardrails,"Environment switching, timeout standards, artifact outputs","playwright,config,env",extended,knowledge/playwright-config.md
+ci-burn-in,CI and Burn-In Strategy,"Staged jobs, shard orchestration, burn-in loops, artifact policy","ci,automation,flakiness",extended,knowledge/ci-burn-in.md
+selective-testing,Selective Test Execution,"Tag/grep usage, spec filters, diff-based runs, promotion rules","risk-based,selection,strategy",extended,knowledge/selective-testing.md
+feature-flags,Feature Flag Governance,"Enum management, targeting helpers, cleanup, release checklists","feature-flags,governance,launchdarkly",specialized,knowledge/feature-flags.md
+contract-testing,Contract Testing Essentials,"Pact publishing, provider verification, resilience coverage","contract-testing,pact,api,backend,microservices,service-contract",specialized,knowledge/contract-testing.md
+email-auth,Email Authentication Testing,"Magic link extraction, state preservation, caching, negative flows","email-authentication,security,workflow",specialized,knowledge/email-auth.md
+error-handling,Error Handling Checks,"Scoped exception handling, retry validation, telemetry logging","resilience,error-handling,stability,api,backend",extended,knowledge/error-handling.md
+visual-debugging,Visual Debugging Toolkit,"Trace viewer usage, artifact expectations, accessibility integration","debugging,dx,tooling,ui",specialized,knowledge/visual-debugging.md
+risk-governance,Risk Governance,"Scoring matrix, category ownership, gate decision rules","risk,governance,gates",core,knowledge/risk-governance.md
+probability-impact,Probability and Impact Scale,"Shared definitions for scoring matrix and gate thresholds","risk,scoring,scale",core,knowledge/probability-impact.md
+test-quality,Test Quality Definition of Done,"Execution limits, isolation rules, green criteria","quality,definition-of-done,tests",core,knowledge/test-quality.md
+nfr-criteria,NFR Review Criteria,"Security, performance, reliability, maintainability status definitions","nfr,assessment,quality",extended,knowledge/nfr-criteria.md
+test-levels,Test Levels Framework,"Guidelines for choosing unit, integration, or end-to-end coverage","testing,levels,selection,api,backend,ui",core,knowledge/test-levels-framework.md
+test-priorities,Test Priorities Matrix,"P0–P3 criteria, coverage targets, execution ordering","testing,prioritization,risk",core,knowledge/test-priorities-matrix.md
+test-healing-patterns,Test Healing Patterns,"Common failure patterns and automated fixes","healing,debugging,patterns",core,knowledge/test-healing-patterns.md
+selector-resilience,Selector Resilience,"Robust selector strategies and debugging techniques","selectors,locators,debugging,ui",core,knowledge/selector-resilience.md
+timing-debugging,Timing Debugging,"Race condition identification and deterministic wait fixes","timing,async,debugging",extended,knowledge/timing-debugging.md
+overview,Playwright Utils Overview,"Installation, design principles, fixture patterns for API and UI testing","playwright-utils,fixtures,api,backend,ui",core,knowledge/overview.md
+api-request,API Request,"Typed HTTP client, schema validation, retry logic, operation-based overload for API and service testing","api,backend,service-testing,api-testing,playwright-utils,openapi,codegen,operation",core,knowledge/api-request.md
+network-recorder,Network Recorder,"HAR record/playback, CRUD detection for offline UI testing","network,playwright-utils,ui,har",extended,knowledge/network-recorder.md
+auth-session,Auth Session,"Token persistence, multi-user, API and browser authentication","auth,playwright-utils,api,backend,jwt,token",core,knowledge/auth-session.md
+intercept-network-call,Intercept Network Call,"Network spy/stub, JSON parsing for UI tests","network,playwright-utils,ui",extended,knowledge/intercept-network-call.md
+recurse,Recurse Polling,"Async polling for API responses, background jobs, eventual consistency","polling,playwright-utils,api,backend,async,eventual-consistency",extended,knowledge/recurse.md
+log,Log Utility,"Report logging, structured output for API and UI tests","logging,playwright-utils,api,ui",extended,knowledge/log.md
+file-utils,File Utilities,"CSV/XLSX/PDF/ZIP validation for API exports and UI downloads","files,playwright-utils,api,backend,ui",extended,knowledge/file-utils.md
+burn-in,Burn-in Runner,"Smart test selection, git diff for CI optimization","ci,playwright-utils",extended,knowledge/burn-in.md
+network-error-monitor,Network Error Monitor,"HTTP 4xx/5xx detection for UI tests","monitoring,playwright-utils,ui",extended,knowledge/network-error-monitor.md
+fixtures-composition,Fixtures Composition,"mergeTests composition patterns for combining utilities","fixtures,playwright-utils",extended,knowledge/fixtures-composition.md
+api-testing-patterns,API Testing Patterns,"Pure API test patterns without browser: service testing, microservices, GraphQL","api,backend,service-testing,api-testing,microservices,graphql,no-browser",specialized,knowledge/api-testing-patterns.md
+adr-quality-readiness-checklist,ADR Quality Readiness Checklist,"8-category 29-criteria framework for ADR testability and NFR assessment","nfr,testability,adr,quality,assessment,checklist",extended,knowledge/adr-quality-readiness-checklist.md
+playwright-cli,Playwright CLI,"Token-efficient CLI for AI coding agents: element refs, sessions, snapshots, browser automation","cli,browser,agent,automation,snapshot",core,knowledge/playwright-cli.md

package/src/workflows/testarch/atdd/atdd-checklist-template.md

@@ -2,6 +2,8 @@
 stepsCompleted: []
 lastStep: ''
 lastSaved: ''
+workflowType: 'testarch-atdd'
+inputDocuments: []
 ---
 
 # ATDD Checklist - Epic {epic_num}, Story {story_num}: {story_title}