skills.rest
KarenTenorio963
KarenTenorio963COMMUNITY
Explore all skills by this author →
GitHub

qa-integration

Audits in-memory integration tests against spec acceptance scenarios and adds missing coverage.

Updated Aug 28, 2026
Search Tags:#integration testing#pytest#python#qa#spec kit#test audit#acceptance scenarios
One-click install
npx skills add https://github.com/KarenTenorio963/curso-mcp-karentenorio --skill qa-integration-karentenorio963
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa-integration
Source: https://github.com/KarenTenorio963/curso-mcp-karentenorio/tree/main/entregas/s4/mi-proyecto-speckit/.agents/skills/qa-integration
Command: npx skills add https://github.com/KarenTenorio963/curso-mcp-karentenorio --skill qa-integration-karentenorio963

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Integration test suites often drift out of sync with specification acceptance scenarios, leaving gaps in coverage or duplicating tests that already exist. This Skill audits your existing in-memory integration tests against your Spec Kit specs and adds only what is missing. ## Core Features & Use Cases - Spec-Driven Audit: Reads the Acceptance Scenarios section of specs/*/spec.md to identify flows where two or more of your own modules connect. - Duplicate and Misclassification Detection: Reports scenarios already covered by existing tests and flags subprocess-based tests that are actually misclassified e2e tests. - Gap-Filling Test Generation: Adds only missing in-memory integration tests in tests/integration/ and verifies them with uv run pytest. - Use Case: After running Spec Kit to define a CLI feature, use this Skill to confirm every acceptance scenario involving module-to-module interaction has a real in-memory test, without duplicating existing coverage. ## Quick Start Audit my integration tests against the spec acceptance scenarios and add any missing in-memory tests.

Frequently Asked Questions about qa-integration

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

FAQPage Schema
How do I write integration tests that match my spec acceptance scenarios?▼

Read the Acceptance Scenarios section of your spec.md file and identify flows where two or more of your own modules connect. Write in-memory tests that call those functions directly, then run pytest on tests/integration/ to verify.

What is the difference between integration tests and e2e tests in pytest?▼

Integration tests call your modules' functions directly in memory to verify they connect correctly. Tests that use subprocess to launch the full program are end-to-end tests, even if placed in tests/integration/, and should be reclassified.

Can I use this Skill without Spec Kit specs?▼

No. The Skill requires an existing specs/*/spec.md file with Acceptance Scenarios to audit against. If no spec exists, it stops and instructs you to run Spec Kit first.

Why should integration tests avoid subprocess calls?▼

Subprocess launches the entire program as a separate process, which tests the full system end-to-end rather than module integration. In-memory tests run faster, give clearer failure signals, and isolate the connection between specific modules.

How do I avoid duplicating existing integration test coverage?▼

Review the existing files in tests/integration/ before writing anything to determine which flows they already test. Report covered scenarios as already covered and only add tests for gaps.

Related Skills

Explore More Software Engineering Skills→
alex-jordan547alex-jordan547

speckit-checklist

Generate quality checklists that validate requirements completeness and clarity in spec-kit projects.

Community
Intermediate
bismuthdigitalbismuthdigital

test

Run Python test suites with pytest and generate coverage reports.

Official
Intermediate
agentopologyagentopology
99

parser-dev

Automate parser development tasks across grammars, bindings, tests, CLI, and documentation.

Official
Advanced
oleg-vasilyevoleg-vasilyev

write-a-spec

Write and review Vitest unit specs with strict mocking, stub, and mutation-testing rules.

Community
Advanced