bmad-qa-generate-e2e-tests

Generate API and end-to-end automated tests for implemented features using the project's existing test framework.

1|Updated Jun 2, 2026
One-click install
npx skills add https://github.com/SevWren/Daily-Motivation-Brain-Helper --skill bmad-qa-generate-e2e-tests-sevwren
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-qa-generate-e2e-tests
Source: https://github.com/SevWren/Daily-Motivation-Brain-Helper/tree/main/.claude/skills/bmad-qa-generate-e2e-tests
Command: npx skills add https://github.com/SevWren/Daily-Motivation-Brain-Helper --skill bmad-qa-generate-e2e-tests-sevwren

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing automated tests for already-implemented features is repetitive and often skipped, leaving code without regression coverage. This Skill generates API and E2E tests that match your project's existing test framework and verifies they actually pass. ## Core Features & Use Cases - Framework Detection: Scans package.json and existing test files to detect Playwright, Jest, Vitest, Cypress, or other frameworks, then follows the project's established patterns. - API Test Generation: Creates tests covering status codes, response structure validation, happy paths, and critical error cases for endpoints and services. - E2E Test Generation: Builds UI workflow tests using semantic locators (roles, labels, text) that assert visible outcomes without hardcoded waits. - Use Case: After shipping a new checkout flow, ask the Skill to generate tests for the checkout feature; it detects Playwright, writes linear user-workflow tests, runs them, fixes failures, and saves a coverage summary to your implementation artifacts folder. ## Quick Start Ask the assistant to create QA automated tests for a specific feature or directory in your project.

Frequently Asked Questions about bmad-qa-generate-e2e-tests

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate E2E tests for an existing feature?

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

What test frameworks does this QA automation workflow support?

It works with whatever framework the project already uses, detected from package.json dependencies such as Playwright, Jest, Vitest, or Cypress. If no framework exists, it analyzes the stack and suggests an appropriate one.

Can it generate API tests as well as UI tests?

Yes, it generates API tests covering status codes like 200, 400, 404, and 500, response structure validation, and happy path plus one or two error cases. UI tests are generated separately when the feature has a user interface.

What happens if the generated tests fail when run?

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

When should I use the Test Architect module instead?

Use the Test Architect (TEA) module when you need risk-based test strategy, test design planning, quality gates, NFR assessment, or comprehensive coverage analysis. This Skill focuses on straightforward happy-path and critical-error test generation.