bmad-qa-generate-e2e-tests

Generate API and UI end-to-end tests for implemented features.

Updated Mar 24, 2026
One-click install
npx skills add https://github.com/imonmi/INTER-EDU --skill bmad-qa-generate-e2e-tests-imonmi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-qa-generate-e2e-tests
Source: https://github.com/imonmi/INTER-EDU/tree/main/_bmad/bmm/workflows/bmad-qa-generate-e2e-tests
Command: npx skills add https://github.com/imonmi/INTER-EDU --skill bmad-qa-generate-e2e-tests-imonmi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual QA for new features is time-consuming and error-prone, delaying releases and risking regressions.

Core Features & Use Cases

  • Automatically generate API and E2E tests for implemented features, following the project's existing test framework and conventions.
  • Cover happy paths and critical error scenarios to improve stability and confidence in deployments.
  • Use case: When a feature is added or updated, run generated tests to verify core workflows and detect regressions early.

Quick Start

Run the skill to generate tests for the specified feature, and review the resulting test suites in the project's tests directory.

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 automate end-to-end tests for a new feature in my codebase?

You can automate end-to-end tests by generating test suites that adapt to your project's existing framework patterns and conventions. The generated tests cover API and UI layers, validating common scenarios and aligning with the repository's test command.

What is the best way to generate regression tests for implemented features?

The best way to generate regression tests is to automatically create E2E test suites that cover happy paths and critical error scenarios. This approach improves stability and detects regressions early when features are added or updated.

Can I generate E2E tests that follow my project's existing test framework conventions?

Yes, the generated E2E tests adapt to existing framework patterns and project conventions within your codebase. They align with the repository's test command to ensure seamless integration and accurate QA coverage.

Does automated QA test generation cover both API and UI layers?

Yes, automated QA test generation applies across both API and UI layers within the project's codebase. It validates common scenarios and documents outcomes to enforce test quality and ensure robust coverage.

Why should I use automated E2E test generation instead of manual QA for new features?

You should use automated E2E test generation because manual QA for new features is time-consuming and error-prone. Automation delays releases less, risks fewer regressions, and provides confidence in deployments by verifying core workflows.