bmad-qa-generate-e2e-tests

Generate API and E2E tests for existing features using semantic locators.

4|1|Updated Sep 30, 2024
One-click install
npx skills add https://github.com/co-cddo/ndx --skill bmad-qa-generate-e2e-tests-co-cddo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-qa-generate-e2e-tests
Source: https://github.com/co-cddo/ndx/tree/main/_bmad/bmm/workflows/bmad-qa-generate-e2e-tests
Command: npx skills add https://github.com/co-cddo/ndx --skill bmad-qa-generate-e2e-tests-co-cddo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the generation of end-to-end QA tests for existing features based on user requests, reducing manual test creation time and ensuring consistent coverage.

Core Features & Use Cases

  • Generates API and E2E tests aligned with project conventions, scaffolding test files and summaries.
  • Integrates with the project's test framework to reuse existing patterns and reporting.
  • Use Case: when a feature is implemented or updated, trigger automated QA test generation to validate flows and edge cases.

Quick Start

Describe the feature to test and run the QA generate E2E tests workflow.

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 QA tests for existing features?

You can automate end-to-end QA tests by describing the feature to validate, which triggers generation of API tests, E2E tests, and a concise summary aligned with your project conventions.

Can I generate E2E tests that align with my project's existing test framework?

Yes, E2E test generation integrates directly with your project's test framework, reusing existing patterns and reporting to ensure consistency across your automated verification workflows.

Does automated QA test generation work for both UI and API components?

Automated QA test generation applies to projects with either UI or API components, producing respective API tests and E2E tests with semantic locators for UI validation.

What is the best way to scaffold API and E2E tests after implementing a feature?

The best way to scaffold tests is triggering automated QA generation upon feature completion, which outputs structured test files and a concise summary directly to your designated tests directory.

How does semantic locator usage work in generated E2E UI tests?

Semantic locators in generated E2E UI tests target elements by meaning rather than brittle attributes, ensuring automated test stability and reducing maintenance when UI structures change.

Why do I need to specify a tests directory for E2E test generation?

Specifying a tests directory ensures the generated API tests, E2E tests, and summaries output to the correct location, maintaining project organization and satisfying project testing requirements.