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).