bmad-testarch-automate

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

Updated Sep 3, 2026
One-click install
npx skills add https://github.com/watchthelight/shatterfish --skill bmad-testarch-automate-watchthelight
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-testarch-automate
Source: https://github.com/watchthelight/shatterfish/tree/main/.claude/skills/bmad-testarch-automate
Command: npx skills add https://github.com/watchthelight/shatterfish --skill bmad-testarch-automate-watchthelight

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Expanding test automation coverage across a codebase is slow and inconsistent when done by hand. This Skill analyzes your source code or BMad artifacts, identifies coverage gaps, and generates a complete, prioritized test suite with supporting fixtures, 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 Modes: Runs in BMad-Integrated, Standalone, or Auto-discover mode, with parallel subagent orchestration and optional self-healing of failing tests. - Use Case: Point it at an untested feature directory like src/orders/refunds/ and receive a full suite of tagged Playwright specs, factories, an automation summary, and updated package.json test scripts. ## Quick Start Ask the agent to expand test coverage for a specific feature or the whole codebase, for example by saying "lets expand test coverage 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?

Run the automate workflow in Standalone or Auto-discover mode. It scans your source directory, identifies untested features and coverage gaps, then generates prioritized Playwright tests with fixtures and factories.

What test levels does the automate workflow generate?

It generates E2E, API, component, and unit tests, each tagged with P0-P3 priorities. E2E covers critical user journeys only, while API and unit tests handle business logic variations and edge cases to avoid duplicate coverage.

Does the automate workflow require BMad artifacts like stories or PRDs?

No, BMad artifacts are optional. Without them the workflow switches to Standalone mode and analyzes source code directly. The only hard requirement is an existing test framework config such as playwright.config.ts.

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. It reads provider source or OpenAPI specs before writing each interaction.

What happens when generated tests fail after creation?

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

Why does the workflow halt with a framework error?

The workflow halts when no test framework scaffolding exists, such as a missing playwright.config.ts or cypress.config.ts. Run the framework workflow first to set up scaffolding, then rerun automate.