mirror of
https://github.com/bmad-code-org/BMAD-METHOD.git
synced 2026-01-30 04:32:02 +00:00
e535f94325
Style Guide Additions: - Add Reference Structure section with 6 document types (Index, Catalog, Deep-Dive, Configuration, Glossary, Comprehensive) - Add Glossary Structure section with table-based format leveraging Starlight's right-nav for navigation - Include checklists for both new document types Reference Docs Updated: - agents/index.md: Catalog format, universal commands tip admonition - configuration/core-tasks.md: Configuration format with admonitions - configuration/global-config.md: Table-based config reference - workflows/index.md: Minimal index format - workflows/core-workflows.md: Catalog format - workflows/document-project.md: Deep-dive with Quick Facts admonition - workflows/bmgd-workflows.md: Comprehensive format, removed ~30 hr rules Glossary Rewritten: - Converted from 373 lines with ### headers to 123 lines with tables - Right nav now shows 9 categories instead of 50+ terms - Added italic context markers (*BMGD.*, *Brownfield.*, etc.) - Alphabetized terms within categories - Removed redundant inline TOC All Docs: - Remove horizontal rules (---) per style guide - Remove "Related" sections (sidebar handles navigation) - Standardize admonition usage - Archive deleted workflow customization docs Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2.7 KiB
2.7 KiB
title, description
| title | description |
|---|---|
| How to Run Test Design | How to create comprehensive test plans using TEA's test-design workflow |
Use TEA's *test-design workflow to create comprehensive test plans with risk assessment and coverage strategies.
When to Use This
System-level (Phase 3):
- After architecture is complete
- Before implementation-readiness gate
- To validate architecture testability
Epic-level (Phase 4):
- At the start of each epic
- Before implementing stories in the epic
- To identify epic-specific testing needs
:::note[Prerequisites]
- BMad Method installed
- TEA agent available
- For system-level: Architecture document complete
- For epic-level: Epic defined with stories :::
Steps
1. Load the TEA Agent
Start a fresh chat and load the TEA (Test Architect) agent.
2. Run the Test Design Workflow
*test-design
3. Specify the Mode
TEA will ask if you want:
- System-level — For architecture testability review (Phase 3)
- Epic-level — For epic-specific test planning (Phase 4)
4. Provide Context
For system-level:
- Point to your architecture document
- Reference any ADRs (Architecture Decision Records)
For epic-level:
- Specify which epic you're planning
- Reference the epic file with stories
5. Review the Output
TEA generates a comprehensive test design document.
What You Get
System-Level Output (test-design-system.md):
- Testability review of architecture
- ADR → test mapping
- Architecturally Significant Requirements (ASRs)
- Environment needs
- Test infrastructure recommendations
Epic-Level Output (test-design-epic-N.md):
- Risk assessment for the epic
- Test priorities
- Coverage plan
- Regression hotspots (for brownfield)
- Integration risks
- Mitigation strategies
Test Design for Different Tracks
| Track | Phase 3 Focus | Phase 4 Focus |
|---|---|---|
| Greenfield | System-level testability review | Per-epic risk assessment and test plan |
| Brownfield | System-level + existing test baseline | Regression hotspots, integration risks |
| Enterprise | Compliance-aware testability | Security/performance/compliance focus |
Tips
- Run system-level right after architecture — Early testability review
- Run epic-level at the start of each epic — Targeted test planning
- Update if ADRs change — Keep test design aligned
- Use output to guide other workflows — Feeds into
*atddand*automate
Next Steps
After test design:
- Setup Test Framework — If not already configured
- Implementation Readiness — System-level feeds into gate check
- Story Implementation — Epic-level guides testing during dev