testing-integration
Testing Integration
Overview
Use this skill to verify boundary behavior where independently correct units may still fail in combination.
Scope Boundaries
- Use when correctness depends on integration seams.
- Typical requests:
Validate repository-to-database behavior including failure paths.Test timeout and retry handling between services.Verify adapter replacement does not break boundary contracts.
- Do not use when:
- The goal is full browser journey validation (
testing-e2e/playwright). - The goal is pure isolated unit checks (
testing-unit).
- The goal is full browser journey validation (
Inputs
- Integration seams and dependency topology
- Failure-mode expectations (timeout, retry, partial failure)
- Fixture/environment constraints
Outputs
- Boundary test matrix with dependency strategy
- Decision record for integration depth and tooling choices
- Verification checklist for success and failure semantics
Workflow
- Enumerate high-risk seams and boundary contracts.
- Define required behaviors for success, timeout, and error cases.
- Compare fixture strategies and choose one with rationale.
- Execute focused integration tests with reproducible setup.
- Publish coverage gaps, residual risks, and ownership.
Quality Gates
- Critical seams include failure-path coverage.
- Boundary expectations are explicit and deterministic.
- Evidence can be replayed in CI.
- Dependency assumptions are documented.
Failure Handling
- Stop when critical boundaries lack failure-path tests.
- Escalate when dependency ownership blocks reliable fixtures.
Bundled Resources
references/trigger-and-examples.md: trigger patterns, anti-patterns, and deliverable expectations.
More from kentoshimizu/sw-agent-skills
graph-algorithms
Graph algorithm workflow for modeling entities/relations and selecting traversal, path, ordering, or flow strategies. Use when correctness or performance depends on graph representation and algorithm choice; do not use for schema-only modeling or deployment topology planning.
14bash-style-guide
Style, review, and refactoring standards for Bash shell scripting. Trigger when `.sh` files, files with `#!/usr/bin/env bash` or `#!/bin/bash`, or CI workflow blocks with `shell: bash` are created, modified, or reviewed and Bash-specific quality controls (quoting safety, error handling, portability, readability) must be enforced. Do not use for generic POSIX `sh`, PowerShell, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
11architecture-clean-architecture
Clean Architecture workflow for enforcing dependency direction, stable domain boundaries, and use-case-centered application design. Use when teams must separate business rules from frameworks and delivery mechanisms; do not use for isolated module cleanup without boundary implications.
11powershell-style-guide
Style, review, and refactoring standards for PowerShell scripting. Trigger when `.ps1`, `.psm1`, `.psd1` files, or CI workflow blocks with `shell: pwsh` or `shell: powershell` are created, modified, or reviewed and PowerShell-specific quality controls (error handling, parameter validation, readability, operational safety) must be enforced. Do not use for Bash, generic POSIX `sh`, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
10github-codeowners-management
Govern CODEOWNERS rules so review routing reflects real ownership and risk boundaries on GitHub. Use when repository ownership mapping or mandatory reviewer rules must be defined, updated, or audited; do not use for non-GitHub runtime architecture or data-layer design.
9security-authentication
Security workflow for authentication architecture, credential lifecycle, and session/token assurance. Use when login, identity proofing, MFA, or session security decisions are required; do not use for authorization policy design or non-security quality tuning.
9