Consumer-Driven Contract Testing
Each consumer publishes a contract stating exactly which requests it makes and which response fields it relies on; the provider's CI verifies every consumer contract against the real implementation. This catches breaking API changes without spinning up both services in a shared integration environment.
This Concept is waiting for its first lesson!
Each consumer publishes a contract stating exactly which requests it makes and which response fields it relies on; the provider's CI verifies every consumer contract against the real implementation. This catches breaking API changes without spinning up both services in a shared integration environment.
Are you a teacher? Sign in to start contributing.
Sign In