bmad-qa-generate-e2e-tests

Generates API and end-to-end automated tests for existing project features.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing automated tests for already-implemented features is repetitive and often skipped, leaving codebases without regression coverage. This Skill detects the project's existing test framework and generates runnable API and E2E tests that match its conventions. ## Core Features & Use Cases - Framework Detection: Scans package.json and existing test files to reuse the project's current framework (Playwright, Jest, Vitest, Cypress) 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 using semantic locators. - Run and Verify: Executes the generated tests, fixes failures, and writes a coverage summary to a markdown report. - Use Case: After shipping a new checkout flow, ask for QA automated tests and receive passing Playwright E2E specs plus a test-summary.md report. ## 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 scan. It detects your project's test framework, generates API and UI tests following existing patterns, runs them, and saves a summary report.

What test frameworks does automated test generation 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 suggests a framework based on the project type.

Can I generate tests for both API endpoints and UI features?▼

Yes. API tests cover status codes and response structure with happy path plus error cases, while E2E tests cover user workflows using semantic locators like roles, labels, and text.

What happens if the generated tests fail when run?▼

The workflow executes the tests after generation and fixes any failures immediately before finishing. It only completes once the tests pass and the summary report is written.

When should I use the Test Architect module instead?▼

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