integration-test-designer

Integration testing at the module layer validates real service, database, auth, and permission boundaries together, catching wiring breaks that isolated unit mocks miss while avoiding the overhead of browser-based end-to-end testing.

Service tests passing in isolation but failing in staging indicates broken database or permission wiring. Integration test design reproduces the real failure path by exercising real auth-context minting and persisted-state assertions instead of isolated unit mocks.

Seeded data isolation for integration testing requires defining explicit cleanup strategies and boundary classification for each dependency. The suite stays honest about what is under test by mapping real versus faked seams across services, repositories, and background jobs.

Integration testing does not replace browser tests but reroutes security-matrix and contract concerns to appropriate skills. It validates auth middleware and permission checks through real production-like code paths at the module layer, proving wiring without browser journeys.

Adding negative and permission-denied cases to integration testing involves explicit boundary classification and real-path auth minting. The design covers invalid-input, permission-denied, and seam-failure scenarios while rerouting browser, contract, and security-matrix concerns to specialized skills.