ldy26098
/
BMAD-METHOD
mirror of https://github.com/bmad-code-org/BMAD-METHOD.git
1
0
Fork 0
Code Packages Projects Releases Wiki Activity

docs: spell out acronyms in TEA Lite quickstart 

- MCP → Model Context Protocol
- E2E → End-to-end (also fix missing article)
- CI/CD → Continuous integration/continuous deployment
- ATDD → Acceptance Test-Driven Development
- TDD → Test-Driven Development
- NFR → non-functional requirements
- Remove inaccurate CRUD reference

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
forcetrainer 2026-01-15 21:15:40 -05:00
parent c98849ea80
commit 7d39a2bbdd
1 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
docs/tutorials/getting-started/tea-lite-quickstart.md
View File

@ -58,7 +58,7 @@ When prompted:
- **Planning artifacts folder:** Keep default - **Planning artifacts folder:** Keep default
- **Implementation artifacts folder:** Keep default - **Implementation artifacts folder:** Keep default
- **Project knowledge folder:** Keep default - **Project knowledge folder:** Keep default
- **Enable TEA Playwright MCP enhancements?** Choose "No" for now (we'll explore this later) - **Enable TEA Playwright Model Context Protocol (MCP) enhancements?** Choose "No" for now (we'll explore this later)
- **Using playwright-utils?** Choose "No" for now (we'll explore this later) - **Using playwright-utils?** Choose "No" for now (we'll explore this later)
BMad is now installed! You'll see a `_bmad/` folder in your project. BMad is now installed! You'll see a `_bmad/` folder in your project.
@ -90,9 +90,9 @@ A: "We're testing a React web application (TodoMVC)"
A: "Playwright" A: "Playwright"
**Q: Testing scope?** **Q: Testing scope?**
A: "E2E testing for web application" A: "End-to-end (E2E) testing for a web application"
**Q: CI/CD platform?** **Q: Continuous integration/continuous deployment (CI/CD) platform?**
A: "GitHub Actions" (or your preference) A: "GitHub Actions" (or your preference)
TEA will generate: TEA will generate:
@ -127,7 +127,7 @@ In your chat with TEA, run:
A: "Epic-level - I want to test TodoMVC's basic functionality" A: "Epic-level - I want to test TodoMVC's basic functionality"
**Q: What feature are you testing?** **Q: What feature are you testing?**
A: "TodoMVC's core CRUD operations - creating, completing, and deleting todos" A: "TodoMVC's core operations - creating, completing, and deleting todos"
**Q: Any specific risks or concerns?** **Q: Any specific risks or concerns?**
A: "We want to ensure the filter buttons (All, Active, Completed) work correctly" A: "We want to ensure the filter buttons (All, Active, Completed) work correctly"
@ -358,8 +358,8 @@ This tutorial used `*automate` to generate tests for **existing features** (test
- Want to add test coverage - Want to add test coverage
- Tests should pass on first run - Tests should pass on first run
**When to use `*atdd`:** **When to use `*atdd` (Acceptance Test-Driven Development):**
- Feature doesn't exist yet (TDD workflow) - Feature doesn't exist yet (Test-Driven Development workflow)
- Want failing tests BEFORE implementation - Want failing tests BEFORE implementation
- Following red → green → refactor cycle - Following red → green → refactor cycle
@ -397,7 +397,7 @@ See [TEA Overview](/docs/explanation/features/tea-overview.md) for engagement mo
### Go Full TEA Integrated ### Go Full TEA Integrated
Want the complete quality operating model? Try TEA Integrated with BMad Method: Want the complete quality operating model? Try TEA Integrated with BMad Method:
- Phase 2: Planning with NFR assessment - Phase 2: Planning with non-functional requirements (NFR) assessment
- Phase 3: Architecture testability review - Phase 3: Architecture testability review
- Phase 4: Per-epic test design → ATDD → automate - Phase 4: Per-epic test design → ATDD → automate
- Release Gate: Coverage traceability and gate decisions - Release Gate: Coverage traceability and gate decisions