bmad-testarch-automate

Run the automate workflow in standalone mode by specifying a target feature or files, or let auto-discover scan the source directory. It analyzes coverage gaps, selects appropriate test levels, and generates prioritized tests with fixtures and factories.

It supports Playwright and Cypress for frontend, Maestro for mobile, and backend frameworks like pytest, JUnit, Go test, xUnit, and RSpec. Framework scaffolding such as playwright.config.ts 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 mode that analyzes source code directly without halting.

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. It performs provider source scrutiny before generating interactions.

The workflow halts when no test framework configuration like playwright.config.ts or cypress.config.ts is found, since scaffolding is a hard requirement. Run the framework workflow first to set up the test infrastructure.

When auto_heal_failures is enabled, failing tests are analyzed for patterns like stale selectors, race conditions, or hard waits, then fixed and re-run up to three iterations. Unfixable tests are marked with test.fixme() and detailed comments.