What problem does it solve?
Contract testing prevents brittle, cross-service breakages by ensuring a provider continues to satisfy a consumer’s explicitly recorded expectations at the interface boundary.
Core Features & Use Cases
- Consumer-driven contract artifacts: Capture exactly what the consumer relies on (behavior and specific interactions), not just the provider’s declared shape.
- Two-phase verification with replay: Validate compatibility first on the consumer side (mock/provider replay) and then on the provider side (real provider replay).
- Broker-enabled deploy gating: Use a contract broker to track compatibility versions and block deployments when the provider no longer satisfies the production consumer contract.
Use this when multiple services or components depend on a shared interface and you need deterministic checks that reduce flaky end-to-end staging failures.
Quick Start
Use the contract-testing skill to design a consumer-driven contract for a specific consumer-provider interaction, then set up provider-side replay to verify the provider still satisfies that contract on every change.