bmad-testarch-automate

Generates prioritized E2E, API, component, and unit tests with fixtures and coverage summaries.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/ArchaonHW/MingGoRTS --skill bmad-testarch-automate-archaonhw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-testarch-automate
Source: https://github.com/ArchaonHW/MingGoRTS/tree/main/.agents/skills/bmad-testarch-automate
Command: npx skills add https://github.com/ArchaonHW/MingGoRTS --skill bmad-testarch-automate-archaonhw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Expanding test automation coverage across an existing codebase is slow and inconsistent: teams must decide which features need tests, pick the right test level, avoid duplicate coverage, and keep tests deterministic. This Skill automates that analysis and generates a prioritized test suite with supporting fixtures, factories, and a coverage summary. ## Core Features & Use Cases - Coverage Analysis and Targeting: Scans the codebase or BMad artifacts (story, PRD, tech-spec) to identify untested features, then assigns P0-P3 priorities and selects E2E, API, component, or unit levels per target. - Multi-Stack Test Generation: Detects frontend, backend, fullstack, or mobile stacks and dispatches parallel subagents to generate Playwright, Maestro, or backend framework tests with Given-When-Then structure and data factories. - Contract Testing and Healing: Optionally generates Pact consumer-driven contract tests with provider source scrutiny, and can auto-heal failing tests (selector, timing, data fixes) with a healing report. - Use Case: After implementing a refund-processing feature, run the workflow to produce 39 prioritized tests across API, E2E, and contract levels, plus fixtures, factories, package.json scripts, and an automation summary. ## Quick Start Ask the assistant to expand test coverage for a target feature or the whole codebase, for example by saying "let's expand test coverage for the refunds module".

Frequently Asked Questions about bmad-testarch-automate

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

FAQPage Schema
How do I expand test coverage for an existing codebase?

Run the automate workflow in standalone mode: it scans your source directory, identifies untested features, assigns P0-P3 priorities, and generates tests at the appropriate level (E2E, API, component, unit) with fixtures and factories.

What test frameworks does the automate workflow support?

It supports Playwright and Cypress for frontend, Maestro for mobile, and backend frameworks such as pytest, JUnit, Go test, xUnit, and RSpec. It auto-detects the stack from project manifests like package.json, pom.xml, or pubspec.yaml.

Does the workflow require BMad artifacts like stories or PRDs?

No, BMad artifacts are optional. Without them the workflow runs in standalone or auto-discover mode, analyzing source code directly. The only hard requirement is an existing test framework configuration such as playwright.config.ts.

Can it generate Pact contract tests for microservices?

Yes, when the pactjs-utils flag is enabled and a consumer-provider boundary exists, it generates consumer contract tests and provider verification using createProviderState and buildVerifierOptions, with mandatory provider source scrutiny before each interaction.

What happens when generated tests fail?

If auto-healing is enabled, the workflow identifies failure patterns (stale selectors, race conditions, hardcoded data) and applies fixes up to three iterations. Unfixable tests are marked with test.fixme() and a detailed comment explaining the failure.

When should I not use this test automation workflow?

Do not use it before scaffolding a test framework; it halts if no framework config exists and directs you to run the framework workflow first. It also does not replace ATDD or test review workflows, which run separately.