bmad-qa-generate-e2e-tests

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

1|Updated Apr 27, 2026
One-click install
npx skills add https://github.com/peshay/portfolixir --skill bmad-qa-generate-e2e-tests-peshay
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-qa-generate-e2e-tests
Source: https://github.com/peshay/portfolixir/tree/main/.claude/skills/bmad-qa-generate-e2e-tests
Command: npx skills add https://github.com/peshay/portfolixir --skill bmad-qa-generate-e2e-tests-peshay

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires resolve_customization.py, scripts, config.yaml, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the generation of end-to-end automated tests for existing features, eliminating manual testing processes.

Core Features & Use Cases

  • Feature Generation: Generates automated API and E2E tests for implemented code.
  • User Role: Designed for QA automation engineers who generate tests but do not engage in code review.
  • Test Framework Integration: Works with existing test frameworks or suggests one based on the project's type.
  • Test Output: Provides a markdown summary of the generated tests and their coverage.

Quick Start

Activate the bmad-qa-generate-e2e-tests skill with the command: 'bmad-qa-generate-e2e-tests create qa automated tests for [feature]'.

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 E2E tests for existing features without manual coding?

To automate E2E tests for implemented features, this skill generates API and UI tests automatically by analyzing project context files, eliminating manual test scripting for QA engineers.

Can I generate automated tests for an existing test framework?

Yes, automated test generation adapts to your existing test frameworks or suggests one based on your project type to ensure integration with your current QA automation workflow.

How do I get test coverage statistics after generating E2E tests?

You get test coverage statistics by reviewing the generated markdown summary, which details the automated API and E2E tests produced and their coverage for the implemented features.

What project context is required to generate API and UI tests?

Generating API and UI tests requires access to the project's working directory and project context files to accurately analyze implemented features and produce matching automated tests.