SKILL56quality-testing
Testing Integration Boundaries
Verifies the real contracts where code crosses databases, filesystems, queues, network services, or other independently behaving dependencies.
Primary benefit
Finds serialization, persistence, protocol, and failure-mode defects that mocks and isolated unit tests cannot prove away.When to use
Use when code crosses a database, filesystem, queue, network API, process, or module boundary and isolated tests cannot prove serialization, persistence, protocol, or failure behavior.
When not to use
Do not use when the behavior is fully deterministic inside one unit and no external contract or side effect participates in the risk.
Use cases
Verify repository behavior against the real database engine used by the application
Test how an API client parses success and failure responses at the service boundary
Example prompts
Use testing-integration-boundaries to identify the real dependency boundary here and design the narrowest integration test that proves its contract.Install this skill
Choose the command for your operating system and run it from the repository root.
Bash
./install.sh --skill testing-integration-boundariesPowerShell
./install.ps1 --skill testing-integration-boundariesChatGPT
Download Skill ZIPCompatibility
- Surfaces
- ChatGPT · Codex · Claude Code
- Operating systems
- Linux · macOS · Windows
- Install modes
- PluginFilesystem
Dependencies
No external dependencies
Part of systems
Curated systems that canonically include this method.
Used in evidence
Reports that explicitly list this method among the applied methods.