API Contract Testing

Scope Boundaries

• Use when API compatibility must be continuously validated between producers and consumers.
• Use proactively when schema/endpoint/protocol diffs exist but executable compatibility evidence is missing.
• Use when compatibility judgment is currently human-only and needs codified CI gates.
• Do not use for API schema design from scratch; use api-design-*.
• Do not use for end-to-end UI validation.

Goal

Catch contract drift before deployment impacts consumers.