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

How to Set Up a Test Framework with TEA

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

  • 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

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

framework

TEA will ask about:

  • Your tech stack (React, Node, etc.)
  • Preferred test framework (Playwright, Cypress, Jest)
  • Testing scope (E2E, integration, unit)
  • CI/CD platform (GitHub Actions, etc.)

TEA generates:

  • Test scaffold — Directory structure and config files
  • Sample specs — Example tests following best practices
  • .env.example — Environment variable template
  • .nvmrc — Node version specification
  • README updates — Testing documentation
tests/
├── e2e/
│ ├── example.spec.ts
│ └── fixtures/
├── integration/
├── unit/
├── playwright.config.ts # or cypress.config.ts
└── README.md

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

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.

  • 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

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