bmad-qa-generate-e2e-tests

Specify a feature name, component, or directory to scan, and the Skill generates E2E tests using your project's existing framework. Tests use semantic locators like roles and labels, cover user workflows, and are executed to confirm they pass.

It detects whatever framework the project already uses by inspecting package.json dependencies and existing test files, including Playwright, Jest, Vitest, and Cypress. If none exists, it analyzes the stack and suggests an appropriate framework.

Yes, API test generation works independently of UI tests. It creates tests validating status codes like 200, 400, 404, and 500, checks response structure, and covers the happy path plus one or two error cases.

The Skill runs the tests using the project's test command and fixes failures immediately before finishing. It then validates the result against a checklist covering test quality, independence, and proper locators.

It intentionally avoids complex fixtures, risk-based test strategy, and NFR assessment. For advanced needs like quality gates and comprehensive coverage analysis, the documentation points to the separate Test Architect (TEA) module.