bmad-testarch-automate

Coordinate TEA workflows to generate and validate tests across a codebase.

88|24|Updated Jan 18, 2026

Search Tags:#validation #subagents #aggregation #workflows #test-automation #knowledge-fragments

Ready to run

npx skills add https://github.com/bmad-code-org/bmad-method-test-architecture-enterprise --skill bmad-testarch-automate-bmad-code-org

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bmad-testarch-automate
Source: https://github.com/bmad-code-org/bmad-method-test-architecture-enterprise/tree/main/src/workflows/testarch/bmad-testarch-automate
Command: npx skills add https://github.com/bmad-code-org/bmad-method-test-architecture-enterprise --skill bmad-testarch-automate-bmad-code-org

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Expands TEA-driven test automation coverage across a codebase by coordinating workflows, target discovery, test generation, and validation.

Core Features & Use Cases

Deterministic workflow orchestration across TEA agent and subagents to cover E2E, API, component, and unit testing.
Aggregation of subagent outputs into an automation-summary and creation of supporting fixtures and helpers.
Seamless integration with knowledge fragments and the bmad step-file architecture for repeatable results.

Quick Start

Launch the TEA automate workflow on your codebase to expand test coverage using the provided step-files and subagents.

Frequently Asked Questions about bmad-testarch-automate

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

FAQPage Schema

How do I automate test generation across a codebase using subagents?▼

Test generation is automated by coordinating subagents to discover targets, generate tests, and validate results. The workflow applies structured step files and knowledge fragments to expand coverage and aggregates outputs into a final summary.

What is TEA workflow orchestration for test automation?▼

TEA workflow orchestration coordinates agents and subagents to expand test automation coverage. It enforces deterministic execution across E2E, API, component, and unit testing by applying structured step files and aggregating results into an automation summary.

How do I generate test fixtures and helpers during automated test expansion?▼

Test fixtures and helpers are created automatically during the workflow. Subagents aggregate their outputs into an automation-summary while generating supporting fixtures and helpers to ensure repeatable test results across the codebase.

Can I use step files and knowledge fragments to get repeatable test automation results?▼

Yes, step files and knowledge fragments are integrated directly into the workflow architecture. They provide structured, deterministic execution paths that ensure repeatable results when expanding test coverage across different testing layers.

Does deterministic test execution work for E2E, API, component, and unit testing?▼

Deterministic test execution is supported across E2E, API, component, and unit testing. The workflow enforces deterministic execution by coordinating subagents and applying structured step files to validate results consistently.

What is included in the final automation-summary output for test coverage review?▼

The automation-summary output aggregates subagent outputs, created fixtures, and validation results. It provides a final reviewable report of the expanded test coverage achieved through the deterministic workflow execution.