bmad-qa-generate-e2e-tests

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing automated tests for already-implemented features is repetitive and often skipped. This Skill detects your 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), or recommends one for the stack. - API and E2E Test Generation: Creates status-code and response-structure tests for endpoints, plus user-workflow E2E tests with semantic locators for UI features. - Run and Summarize: Executes the generated tests, fixes failures, and saves a markdown summary with coverage metrics. - Use Case: After shipping a new checkout component, ask for QA automated tests and receive passing Playwright E2E specs plus a test-summary.md report. ## Quick Start Ask the agent 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?

Ask the agent to create QA automated tests for a feature name or directory. The skill detects your test framework, generates API and E2E specs following existing patterns, runs them, and saves a summary to the implementation artifacts folder.

Which test frameworks does this QA test generator 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 a recommended framework before generating tests.

Can it generate API tests as well as UI tests?

Yes. For API endpoints it generates tests covering status codes (200, 400, 404, 500), response structure validation, and happy path plus one or two error cases. UI features get E2E tests with semantic locators.

What happens if the generated tests fail?

The workflow runs the tests using the project's test command and fixes failures immediately before completing. A final checklist verifies that all tests pass, use proper locators, and have no hardcoded waits.

When should I use the Test Architect (TEA) module instead?

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