What problem does it solve?
Consumer-driven contract testing prevents breaking changes by making microservices agree on exact request/response (and event) behaviors before teams deploy.
Core Features & Use Cases
- Pact Consumer & Provider Tests: Generate and verify Pact interactions for API behavior, including typical HTTP request/response flows and GraphQL-style payloads.
- Contract Evolution Guardrails: Apply patterns for backward compatibility, optional field additions, and safe deprecation/versioning strategies to reduce coordination risk.
- Async Messaging Contracts: Define and validate message/event contracts (e.g., Kafka-style) so event producers and consumers remain compatible.
- CI/CD Integration: Run provider tests, publish contracts, and verify across multiple services as part of automated pipelines.
Quick Start
Use contract-testing to draft Pact consumer/provider tests for a targeted interaction (for example, an order-service calling a user-service endpoint) and then run Pact verification in CI.