| schemaVersion | "2026-04-11T00:00:00.000Z" |
| skillId | backend/api-integration-testing |
| name | api-integration-testing |
| displayName | API Integration Testing |
| description | Use when working on API integration tests across services, databases, auth, and external dependencies. Focus on contract correctness, realistic fixtures, isolation, and deterministic assertions. |
| aliases | ["api-integration-testing","API Integration Testing","apiintegrationtesting","服务接口","测试策略","integration","服务端","server side","验证"] |
| version | 0.1.0 |
| sourceHash | sha256:c07b2fd7a4c7d5dce6478aead5b6142827679b4614e12e245a69b1bd827564fd |
| domain | backend |
| departmentTags | ["backend-platform"] |
| sceneTags | ["test"] |
API Integration Testing
Use this skill when the task involves API integration tests across services, databases, auth, and external dependencies.
Goal: produce reliable engineering guidance and implementation steps focused on contract correctness, realistic fixtures, isolation, and deterministic assertions.
Working model
- Identify the affected system, data, users, and failure modes.
- Define invariants, inputs, outputs, ownership, and rollback needs.
- Prefer small, auditable changes with explicit validation.
- Call out security, performance, concurrency, and data-loss risks when relevant.
- Finish with concrete verification steps and residual risks.
Rules
- Ground recommendations in the current codebase or runtime evidence.
- Prefer explicit contracts, typed boundaries, and defensive validation.
- Do not hide operational concerns behind generic best practices.
- Include negative cases, edge cases, and failure behavior.
- For review tasks, list findings first with file and line references when possible.
- For test or performance tasks, define the workload, success criteria, and measurement method.
Checklist
- Are assumptions and ownership boundaries explicit?
- Are risky changes reversible or safely deployable?
- Are observability and diagnostics sufficient for production issues?
- Are tests or validation steps targeted to the actual risk?
- Are security and data-integrity concerns addressed?
