bmad-testarch-automate

Generates prioritized E2E, API, component, and unit tests with fixtures and factories for a codebase.

6|Updated Aug 29, 2026
One-click install
npx skills add https://github.com/HordRicJr/Akomagni --skill bmad-testarch-automate-hordricjr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-testarch-automate
Source: https://github.com/HordRicJr/Akomagni/tree/main/bmad-core/.agents/skills/bmad-testarch-automate
Command: npx skills add https://github.com/HordRicJr/Akomagni --skill bmad-testarch-automate-hordricjr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Expanding test automation coverage across an existing codebase is slow and inconsistent when done manually. This Skill analyzes source code or BMad artifacts (stories, PRDs, test designs), identifies coverage gaps, and generates a structured test suite with fixtures, data factories, and helpers. ## Core Features & Use Cases - Multi-level test generation: Produces E2E, API, component, and unit tests with P0-P3 priority tags, avoiding duplicate coverage across levels. - Test infrastructure scaffolding: Creates Playwright fixtures with auto-cleanup, faker-based data factories, and helper utilities, plus optional Pact consumer-driven contract tests. - Adaptive execution and healing: Supports parallel subagent or sequential generation modes, optional auto-validation, and pattern-based healing of failing tests with a healing report. - Use Case: Point it at a feature directory like src/orders/refunds/ and receive a complete test suite with an automation summary, coverage breakdown, and package.json test scripts. ## Quick Start Ask the AI to expand test coverage for a specific feature or the whole codebase, for example by saying you want to automate tests for the checkout 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 automatically?

Run the automate workflow in standalone mode targeting a feature directory or source files. It analyzes coverage gaps, selects appropriate test levels (E2E, API, component, unit), and generates prioritized tests with fixtures and factories.

What test frameworks does this test automation workflow support?

It supports Playwright and Cypress for frontend, backend frameworks like pytest, JUnit, Go test, xUnit, and RSpec, plus Maestro for mobile. Framework scaffolding such as playwright.config.ts must exist before running.

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 to identify untested features and critical paths.

Can it generate Pact contract tests for microservices?

Yes, when the pactjs-utils flag is enabled it generates consumer contract tests and provider verification using createProviderState and buildVerifierOptions, with mandatory provider source scrutiny before writing interactions.

What happens when generated tests fail after creation?

If auto-healing is enabled, the workflow identifies failure patterns such as stale selectors or race conditions, applies fixes, and retries up to three iterations. Unfixable tests are marked with test.fixme() and detailed comments.

When should I not use automated test generation?

Avoid it when no test framework scaffolding exists, since the workflow halts without a config file. Run the framework setup workflow first, and review generated tests before merging into critical suites.