Skip to content
🤖 Consolidated, AI-optimized BMAD docs: llms-full.txt. Fetch this plain text file for complete context.
Test Architect (TEA) Test Architect (TEA)

How to Set Up a Test Framework with TEA

Use TEA’s framework workflow to scaffold a production-ready test framework for your project.

When to Use This

Section titled “When to Use This”
  • No existing test framework in your project
  • Current test setup isn’t production-ready
  • Starting a new project that needs testing infrastructure
  • Phase 3 (Solutioning) after architecture is complete

Steps

Section titled “Steps”

1. Load the TEA Agent

Section titled “1. Load the TEA Agent”

Start a fresh chat and load the TEA (Test Engineering Architect) agent.

2. Run the Framework Workflow

Section titled “2. Run the Framework Workflow”
framework

3. Answer TEA’s Questions

Section titled “3. Answer TEA’s Questions”

TEA will ask about:

  • Your tech stack (React, Node, 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

Section titled “4. Review Generated Output”

TEA generates:

  • Test scaffold — Directory structure and config files (language-idiomatic)
  • Sample specs — Example tests following best practices for your framework
  • .env.example — Environment variable template
  • Version file — .nvmrc (Node.js), .python-version (Python), global.json (.NET), etc.
  • README updates — Testing documentation

What You Get

Section titled “What You Get”

Frontend/Fullstack (Node.js):

tests/
├── e2e/
│   ├── example.spec.ts
│   └── fixtures/
├── integration/
├── unit/
├── playwright.config.ts  # or cypress.config.ts
└── 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

Section titled “Optional: Playwright Utils Integration”

TEA can integrate with @seontechnologies/playwright-utils for advanced fixtures:

Terminal window
npm install -D @seontechnologies/playwright-utils

Enable during BMad installation or set tea_use_playwright_utils: true in config.

Utilities available: api-request, network-recorder, auth-session, intercept-network-call, recurse, log, file-utils, burn-in, network-error-monitor

Optional: MCP Enhancements

Section titled “Optional: MCP Enhancements”

TEA can use Playwright MCP servers for enhanced capabilities:

  • playwright — Browser automation
  • playwright-test — Test runner with failure analysis

Configure in your IDE’s MCP settings.

Tips

Section titled “Tips”
  • Run only once per repository — Framework setup is a one-time operation
  • Run after architecture is complete — Framework aligns with tech stack
  • Follow up with CI setup — Run ci to configure CI/CD pipeline

Next Steps

Section titled “Next Steps”

After test framework setup:

  1. Test Design — Create test plans for system or epics
  2. CI Configuration — Set up automated test runs
  3. Story Implementation — Tests are ready for development