aped-qa

Generate end-to-end and integration tests from completed Acceptance Criteria.

2|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/yabafre/aped-claude --skill aped-qa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aped-qa
Source: https://github.com/yabafre/aped-claude/tree/main/src/templates/skills/aped-qa
Command: npx skills add https://github.com/yabafre/aped-claude --skill aped-qa

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

APED QA removes the guesswork from testing by turning completed Acceptance Criteria into executable end-to-end and integration tests grounded in your real PRD, UX spec, architecture, and story artifacts.

Core Features & Use Cases

  • E2E and Integration Test Generation: Creates both user-journey (E2E) and service/API-level (integration) tests for the selected scope (story, epic, or all completed work).
  • Framework-Aware Scaffolding: Detects your project’s test stack (e.g., Playwright, Cypress, Jest/Vitest, Pytest, etc.) and halts if it cannot identify a supported framework—so you don’t get unusable tests.
  • Coverage-Oriented QA Output: Produces a QA report that lists coverage of Acceptance Criteria, exercised user journeys, integration points tested, and what should be done manually.

Quick Start

Ask to generate QA for a completed story by saying: generate aped qa tests for story ABC-123 (E2E and integration).

Frequently Asked Questions about aped-qa

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate E2E and integration tests from acceptance criteria?

You can generate E2E and integration tests by providing completed story acceptance criteria, which the tool uses to ground executable user-journey and service-level tests in your PRD, UX, and architecture artifacts.

What is a QA coverage report and how does it map to user journeys?

A QA coverage report maps tested integration points and user journeys against acceptance criteria, providing a detailed list of covered automated checks and remaining manual testing steps.

Does the test generation framework detection work with Playwright, Cypress, and Pytest?

Framework detection scans for supported stacks including Playwright, Cypress, Jest, Vitest, and Pytest, applying a hard-stop to prevent unusable test output if no supported framework is identified.

Can I generate QA tests for an entire epic or just individual stories?

You can generate QA tests for individual completed stories, an entire epic, or all completed work, producing executable end-to-end and integration tests for the selected scope.

Why does test generation halt if it cannot find a supported testing framework?

Test generation halts if no supported framework is detected to prevent the creation of unusable tests, ensuring generated output strictly matches your project's identified test stack.