ros/BMAD-METHOD
1
0
Fork 0
mirror of https://github.com/bmad-code-org/BMAD-METHOD.git synced 2026-01-30 04:32:02 +00:00
Code Issues Packages Projects Releases Wiki Activity

fix: addressed Brian 2nd round of comments

Browse Source
This commit is contained in:
murat
2026-01-28 18:47:05 -06:00
parent 6faa25843f
commit 7205451346
3 changed files with 16 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
src/bmm/agents/quinn.agent.yaml
View File

@@ -17,12 +17,7 @@ agent:
Practical and straightforward. Gets tests written fast without overthinking.
'Ship it and iterate' mentality. Focuses on coverage first, optimization later.
principles:
- Fast test generation over perfect architecture
- Coverage first, optimization later
- Standard test framework patterns (no advanced utilities required)
- Works well for beginners and small teams
- Simpler decision-making than full test architecture
- Happy path + critical edge cases = good enough
- Generate API and E2E tests for implemented code
- Tests should pass on first run
critical_actions:

2
src/bmm/module-help.csv
View File

@@ -29,4 +29,4 @@ bmm,4-implementation,Validate Story,VS,35,_bmad/bmm/workflows/4-implementation/c
bmm,4-implementation,Dev Story,DS,40,_bmad/bmm/workflows/4-implementation/dev-story/workflow.yaml,bmad-bmm-dev-story,true,dev,Create Mode,"Story cycle: Execute story implementation tasks and tests then CR then back to DS if fixes needed",,,
bmm,4-implementation,Code Review,CR,50,_bmad/bmm/workflows/4-implementation/code-review/workflow.yaml,bmad-bmm-code-review,false,dev,Create Mode,"Story cycle: If issues back to DS if approved then next CS or ER if epic complete",,,
bmm,4-implementation,Retrospective,ER,60,_bmad/bmm/workflows/4-implementation/retrospective/workflow.yaml,bmad-bmm-retrospective,false,sm,Create Mode,"Optional at epic end: Review completed work lessons learned and next epic or if major issues consider CC",implementation_artifacts,retrospective,
bmm,4-implementation,Automate,QA,45,_bmad/bmm/workflows/qa/automate/workflow.yaml,bmad-bmm-automate,false,quinn,Create Mode,"Generate tests quickly for existing features (not code review) using standard test patterns",implementation_artifacts,"test suite",
bmm,4-implementation,Automate,QA,45,_bmad/bmm/workflows/qa/automate/workflow.yaml,bmad-bmm-automate,false,quinn,Create Mode,"Generate automated API and E2E tests for implemented code using the project's existing test framework (detects Playwright, Jest, Vitest, etc). Use after implementation to add test coverage. NOT for code review or story validation - use CR for that.",implementation_artifacts,"test suite",
Can't render this file because it has a wrong number of fields in line 7.

16
src/bmm/workflows/qa/automate/instructions.md
View File

@@ -1,11 +1,23 @@
# Quinn QA - Automate
**Goal**: Generate tests quickly for existing features using standard test patterns.
**Goal**: Generate automated API and E2E tests for implemented code.
**Scope**: This workflow only generates tests. It does **not** perform code review or story validation (use Code Review `CR` for that).
**Scope**: This workflow generates tests ONLY. It does **not** perform code review or story validation (use Code Review `CR` for that).
## Instructions
### Step 0: Detect Test Framework
Check project for existing test framework:
- Look for `package.json` dependencies (playwright, jest, vitest, cypress, etc.)
- Check for existing test files to understand patterns
- Use whatever test framework the project already has
- If no framework exists:
- Analyze source code to determine project type (React, Vue, Node API, etc.)
- Search online for current recommended test framework for that stack
- Suggest the meta framework and use it (or ask user to confirm)
### Step 1: Identify Features
Ask user what to test: