qa-e2e

Audits end-to-end subprocess tests against spec acceptance scenarios and adds missing coverage.

Updated Aug 28, 2026
One-click install
npx skills add https://github.com/KarenTenorio963/curso-mcp-karentenorio --skill qa-e2e-karentenorio963
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa-e2e
Source: https://github.com/KarenTenorio963/curso-mcp-karentenorio/tree/main/entregas/s4/mi-proyecto-speckit/.agents/skills/qa-e2e
Command: npx skills add https://github.com/KarenTenorio963/curso-mcp-karentenorio --skill qa-e2e-karentenorio963

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? End-to-end test suites often drift out of sync with the acceptance scenarios defined in Spec Kit specifications, leaving real user flows untested or duplicated. This Skill audits existing e2e tests against specs and fills only the gaps. ## Core Features & Use Cases - Spec-Driven Audit: Reads the Acceptance Scenarios section of specs/*/spec.md to identify the real end-to-end flows that must be covered. - Test Reorganization: Detects integration tests that actually launch the full program via subprocess and relocates them to tests/e2e/ using git mv without rewriting them. - Gap-Filling Test Generation: Adds new e2e tests that invoke the complete program through subprocess, verifying stdout and exit codes, then runs uv run pytest tests/e2e/ -v and reports results. - Use Case: After running Spec Kit on a CLI project, invoke this Skill to ensure every acceptance scenario has a corresponding subprocess-based e2e test before release. ## Quick Start Audit my e2e tests against the spec acceptance scenarios and add any missing end-to-end coverage.

Frequently Asked Questions about qa-e2e

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

FAQPage Schema
How do I write end-to-end tests for a CLI program in Python?▼

End-to-end tests for CLI programs should invoke the complete program via subprocess and assert on stdout and exit codes, never calling internal functions directly. This Skill generates exactly that style of test for each uncovered acceptance scenario.

How to align pytest e2e tests with specification acceptance criteria?▼

Read the Acceptance Scenarios section of your spec.md files and map each real user flow to a subprocess-based test. This Skill automates that audit, adding tests only for scenarios not already covered.

What is the difference between integration tests and e2e tests using subprocess?▼

Integration tests typically call internal components, while e2e tests launch the full program as a user would. This Skill detects integration tests that actually use subprocess and moves them to tests/e2e/ with git mv.

What happens if no spec.md file exists when running this audit?▼

The Skill stops immediately and asks you to run Spec Kit first. It requires at least one specs/*/spec.md file with an Acceptance Scenarios section before it can audit or generate any tests.

Does this Skill rewrite my existing e2e tests?▼

No, it never rewrites existing tests. It only relocates misplaced subprocess-based tests with git mv and adds new tests for uncovered scenarios, avoiding duplication of already-covered flows.