bmad-qa-generate-e2e-tests

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

Updated Nov 6, 2025
One-click install
npx skills add https://github.com/skyoxu/godotgame --skill bmad-qa-generate-e2e-tests-skyoxu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-qa-generate-e2e-tests
Source: https://github.com/skyoxu/godotgame/tree/main/.agents/skills/bmad-qa-generate-e2e-tests
Command: npx skills add https://github.com/skyoxu/godotgame --skill bmad-qa-generate-e2e-tests-skyoxu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generating comprehensive QA tests for new features is time-consuming and error-prone, slowing releases and risking quality.

Core Features & Use Cases

  • Automated API and E2E test generation for implemented features.
  • Alignment with project testing conventions and frameworks.
  • Use case: when a feature is added, automatically produce test skeletons that developers can run and refine.

Quick Start

Run the skill with a target feature name to auto-generate tests for that 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 auto-generate API and E2E tests for a new feature?

To auto-generate API and E2E tests, you run this skill with a target feature name. It scans your codebase to produce test skeletons that match your project's existing testing framework and directory structure.

Can I generate tests that match my project's existing testing conventions?

Yes, you can generate tests that match your project's testing conventions. The skill scans your codebase to ensure the produced API and end-to-end test skeletons align with your configured frameworks and directory structures.

What is the best way to automate test generation for critical API endpoints and workflows?

The best way to automate test generation for critical API endpoints is using a codebase scanning tool. This skill analyzes implemented features to ensure coverage of endpoints, user workflows, and critical paths while saving outputs to configured directories.

Do I need to configure specific directories before generating E2E tests?

Yes, you need configured test directories before generating E2E tests. The skill saves the generated API and end-to-end test skeletons directly into these pre-configured project directories to ensure immediate runability.

Why do generated test skeletons need refinement after automated generation?

Generated test skeletons need refinement because the skill provides foundational coverage for API endpoints and user workflows. Developers must run and refine these automated test skeletons to handle specific edge cases and critical paths.

What does codebase scanning for E2E test generation actually do?

Codebase scanning for E2E test generation analyzes your implemented features to produce automated test skeletons. It identifies critical paths and user workflows, ensuring the output matches your project's testing framework and directory structure.