integration-test-designer

What problem does it solve?

This Skill helps you design integration test suites that prove modules work through real service, database, auth, and permission boundaries, catching wiring bugs that unit tests miss without escalating into browser-based end-to-end testing.

Core Features & Use Cases

• Boundary Mapping: Classifies every dependency as real or faked so the suite stays honest about what is actually under test.
• Data and Auth Strategy: Defines seeded data, isolation, cleanup, and real auth-context minting through production-like code paths.
• Negative and Failure Coverage: Adds invalid-input, permission-denied, and seam-failure cases while explicitly rerouting browser, contract, and security-matrix concerns to the right skills.
• Use Case: A service test keeps passing in isolation but staging fails because the DB or permission path is broken; this Skill designs the integration layer that reproduces the real failure path and documents the implementation handoff.

Quick Start

Ask for an integration test design for the target module, including real service, database, auth, and permission boundaries, then require the output to list faked seams, isolation strategy, negatives, and CI placement.