bmad-testarch-automate

Run the automate workflow in standalone mode by specifying a target feature or directory. It analyzes source files, identifies coverage gaps, and generates prioritized tests at the appropriate level (E2E, API, component, or unit) with supporting fixtures and factories.

The workflow supports Playwright and Cypress for frontend, framework-specific runners like pytest, JUnit, Go test, xUnit, and RSpec for backend, and Maestro for mobile. A framework configuration file must exist before running, or the workflow halts.

No, BMad artifacts are optional. The workflow runs in BMad-Integrated mode when stories or test-design documents exist, but falls back to Standalone or Auto-discover mode that analyzes source code directly.

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 for each interaction.

If auto-healing is enabled, the workflow identifies failure patterns (stale selectors, race conditions, hardcoded data) and applies fixes up to three iterations. Tests that cannot be healed are marked with test.fixme() and detailed comments explaining the failure.

The workflow requires existing test framework scaffolding such as playwright.config.ts or cypress.config.ts. If none is found, it halts and instructs you to run the framework setup workflow first before generating tests.