domains / families / software-engineering / api-contract-testing

api-contract-testing

authentic

Design and review API contract tests across providers and consumers. Use for schema changes, compatibility regressions and client integration failures.

When to use

• A response field, endpoint, event schema or error envelope changes.
• A client and server build successfully but disagree at runtime.
• A team needs to distinguish a breaking change from a compatible extension.
• A reported regression needs a minimal provider/consumer reproduction.

When not to use

• Schema conformance does not prove business correctness, performance or access control.
• One consumer cannot establish compatibility for every client, SDK or cached/offline version.
• Provider fixtures and mocks are not live provider evidence; untested integrations remain unverified.
• This skill plans and verifies contracts; it does not deploy APIs or execute migrations.

Skill page

Source