bmad-testarch-framework

Initialize Playwright or Cypress test frameworks with structured steps and configuration.

88|24|Updated Jan 18, 2026
One-click install
npx skills add https://github.com/bmad-code-org/bmad-method-test-architecture-enterprise --skill bmad-testarch-framework-bmad-code-org
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-testarch-framework
Source: https://github.com/bmad-code-org/bmad-method-test-architecture-enterprise/tree/main/src/workflows/testarch/bmad-testarch-framework
Command: npx skills add https://github.com/bmad-code-org/bmad-method-test-architecture-enterprise --skill bmad-testarch-framework-bmad-code-org

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

TEA's Test Framework Setup automates the initialization of a production-grade test framework (Playwright or Cypress) with structured steps, fixtures, and configuration to ensure deterministic starts.

Core Features & Use Cases

  • Framework scaffolding: create directory structures, config files, fixtures, and helpers following the TEA conventions.
  • Step-file orchestrator: two-layer workflow (steps-c for create, steps-v for validate, steps-e for edit) with frontmatter-driven routing.
  • Activation & customization: resolves workflow blocks using customize.toml and team/user overrides, with persistent facts.

Quick Start

Choose Playwright or Cypress and let TEA scaffold a complete test framework with fixtures, configuration, and documentation.

Frequently Asked Questions about bmad-testarch-framework

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Playwright or Cypress test framework setup for a full-stack project?

Automating test framework setup scaffolds directory structures, config files, fixtures, and helpers following deterministic conventions. It applies to frontend, backend, and full-stack projects, guiding environment setup and documentation through structured workflow steps.

What is a step-file orchestrator and how does it structure test framework initialization?

A step-file orchestrator structures initialization using a two-layer workflow with frontmatter-driven routing. It separates steps into create, validate, and edit phases to produce repeatable, auditable test frameworks that teams can customize per project.

Can I customize the test framework scaffolding with team-specific overrides?

You can customize the test framework scaffolding using a customize.toml file and team or user overrides. The workflow resolves customization blocks and applies persistent facts to ensure the generated framework fits your specific project requirements.

Does this test framework setup work for both frontend and backend environments?

This test framework setup works for frontend, backend, and full-stack environments. It applies knowledge-base patterns, activation hooks, and resolvers to generate a production-grade Playwright or Cypress configuration tailored to your specific stack.

What's the best way to generate a production-grade test framework with fixtures and configuration?

The best way to generate a production-grade test framework is using a deterministic workflow that enforces knowledge-base patterns. This ensures repeatable, auditable scaffolding of fixtures, configuration, and documentation for either Playwright or Cypress.