bmad-qa-generate-e2e-tests

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing automated tests for already-implemented features is repetitive and often skipped. This Skill detects the project's existing test framework, generates API and E2E tests for chosen features, runs them, and produces a coverage summary. ## Core Features & Use Cases - Framework Detection: Scans package.json and existing test files to reuse the project's current framework (Playwright, Jest, Vitest, Cypress, etc.) instead of imposing a new one. - API and E2E Test Generation: Creates status-code and response-structure tests for endpoints, plus user-workflow UI tests with semantic locators. - Execution and Summary: Runs the generated tests, fixes failures, and writes a markdown summary with coverage metrics to the configured output path. - Use Case: After shipping a new checkout flow, ask the Skill to create QA automated tests for the checkout feature; it generates Playwright E2E specs, verifies they pass, and saves a test summary. ## 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?

Invoke the Skill with the feature name or directory to test. It detects your project's test framework, generates API and UI tests following existing patterns, runs them, and saves a summary with coverage metrics.

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 none exists, it analyzes the stack and suggests an appropriate framework.

Can I use this for API testing without a UI?

Yes. For API endpoints and services it generates tests covering status codes (200, 400, 404, 500), response structure validation, and happy path plus one or two error cases, skipping E2E generation when no UI exists.

What happens when generated tests fail to run?

The workflow executes the tests with the project's test command and fixes failures immediately before completing. It only finishes once all generated tests pass and the summary is written.

What are the limitations of this test generation approach?

It intentionally avoids complex fixtures, over-engineering, and advanced patterns like risk-based strategy or NFR assessment. For those needs, the documentation points to the separate Test Architect (TEA) module.