External/BMAD-METHOD
1
0
Fork 0
mirror of https://github.com/bmadcode/BMAD-METHOD.git synced 2025-12-29 16:14:59 +00:00
Code Issues Packages Projects Releases Wiki Activity

Port TEA commands into workflows and preload Murat knowledge (#660)

Browse Source 
* Port TEA commands into workflows and preload Murat knowledge

* Broke the giant knowledge dump into curated fragments under src/modules/bmm/testarch/knowledge/

* Broke the giant knowledge dump into curated fragments under src/modules/bmm/testarch/knowledge/

* updated the web bunles for tea, and spot updates for analyst and sm

* Replaced the old TEA brief with an indexed knowledge system: the agent now loads topic-specific
  docs from knowledge/ via tea-index.csv, workflows reference those fragments, and risk/level/
  priority guidance lives in the new fragment files

---------

Co-authored-by: Murat Ozcan <murat@mac.lan>
This commit is contained in:
Murat K Ozcan
2025-09-30 15:19:55 -05:00
committed by GitHub
parent 30fb0e67e1
commit df0c3e4bae
51 changed files with 1139 additions and 901 deletions
Download Patch File Download Diff File Expand all files Collapse all files

44
src/modules/bmm/workflows/testarch/automate/instructions.md Normal file
View File

@@ -0,0 +1,44 @@
<!-- Powered by BMAD-CORE™ -->
# Automation Expansion v3.0
```xml
<task id="bmad/bmm/testarch/automate" name="Automation Expansion">
<llm critical="true">
<i>Preflight requirements:</i>
<i>- Acceptance criteria are satisfied.</i>
<i>- Code builds locally without errors.</i>
<i>- Framework scaffolding is configured.</i>
</llm>
<flow>
<step n="1" title="Preflight">
<action>Verify all requirements above; halt if any fail.</action>
</step>
<step n="2" title="Expand Automation">
<action>Review story source/diff to confirm automation targets.</action>
<action>Use `{project-root}/bmad/bmm/testarch/tea-index.csv` to load fragments such as `fixture-architecture`, `selective-testing`, `ci-burn-in`, `test-quality`, `test-levels`, and `test-priorities` before proposing additions.</action>
<action>Ensure fixture architecture exists (Playwright `mergeTests`, Cypress commands); add apiRequest/network/auth/log fixtures if missing.</action>
<action>Map acceptance criteria using the `test-levels` fragment to avoid redundant coverage.</action>
<action>Assign priorities using the `test-priorities` fragment so effort follows risk tiers.</action>
<action>Generate unit/integration/E2E specs (naming `feature-name.spec.ts`) covering happy, negative, and edge paths.</action>
<action>Enforce deterministic waits, self-cleaning factories, and execution under 1.5 minutes per test.</action>
<action>Run the suite, capture Definition of Done results, and update package.json scripts plus README instructions.</action>
</step>
<step n="3" title="Deliverables">
<action>Create new/enhanced spec files grouped by level, supporting fixtures/helpers, data factory utilities, updated scripts/README notes, and a DoD summary highlighting remaining gaps.</action>
</step>
</flow>
<halt>
<i>If the automation target is unclear or the framework is missing, halt and request clarification/setup.</i>
</halt>
<notes>
<i>Never create page objects; keep tests under 300 lines and stateless.</i>
<i>Forbid hard waits/conditional flow; co-locate tests near source.</i>
<i>Flag flaky patterns immediately.</i>
<i>Reference `tea-index.csv` tags (e.g., fixture-architecture, selective-testing, ci-burn-in) to load the right fragment instead of the entire knowledge bundle.</i>
</notes>
<output>
<i>Prioritized automation suite updates and DoD summary ready for gating.</i>
</output>
</task>
```