bmad-qa-generate-e2e-tests

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

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/ArchaonHW/MingGoRTS --skill bmad-qa-generate-e2e-tests-archaonhw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-qa-generate-e2e-tests
Source: https://github.com/ArchaonHW/MingGoRTS/tree/main/.agents/skills/bmad-qa-generate-e2e-tests
Command: npx skills add https://github.com/ArchaonHW/MingGoRTS --skill bmad-qa-generate-e2e-tests-archaonhw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing automated API and E2E tests for newly implemented features is repetitive and often skipped under deadline pressure. This Skill automates test generation by detecting the project's existing test framework, producing tests that follow established patterns, running them, and fixing failures until they pass. ## Core Features & Use Cases - Framework Detection: Scans package.json and existing test files to reuse the project's current test framework (Playwright, Jest, Vitest, Cypress, etc.) instead of imposing a new one. - API and E2E Test Generation: Creates API tests covering status codes and response structures, plus E2E tests using semantic locators for user workflows. - Run-and-Fix Loop: Executes generated tests and immediately fixes failures, then produces a markdown coverage summary. - Use Case: After implementing a new checkout endpoint and UI flow, ask the Skill to generate tests; it detects Playwright in the repo, writes API and E2E specs, runs them, fixes any failures, and saves a test summary report. ## Quick Start Create QA automated tests for the checkout feature and verify they all pass.

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 semantic locators like roles, labels, and text. Tests follow your project's existing framework patterns and are executed to confirm they pass.

What test frameworks does this QA automation workflow support?

It supports 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 source code and suggests an appropriate one for the stack.

Can it generate API tests as well as UI tests?

Yes, it generates API tests covering status codes like 200, 400, 404, and 500, plus response structure validation. UI end-to-end tests are generated separately when the project has a user interface.

What happens when generated tests fail?

The workflow runs the generated tests using the project's test command and fixes any failures immediately before finishing. A final markdown summary lists generated tests and coverage metrics.

When should I use the Test Architect module instead?

Use the Test Architect (TEA) module when you need risk-based test strategy, quality gates, NFR assessment, or comprehensive coverage analysis. This Skill intentionally focuses on happy paths and one to two critical error cases.