Consumer-Driven Contracts
Consumers declaring what they rely on, and providers verifying against those declarations.
3 to work through
-
intermediate Multiple choice
A provider service has 40 consumers and a 15-minute pipeline. Contract tests already exist and the provider still breaks consumers in production. Which change actually fixes it?
2 min answer -
advanced
A consumer's contract file is regenerated from its own test suite on every build and published to the broker. A developer on the consumer team deletes an obsolete test that happened to be the only one exercising the refund_reason field. Nobody notices at the time. What happens over the following two months?
3 min answer -
advanced
Why are consumer-driven contracts more useful than provider-published schemas, and what does the direction change?
2 min answer
3 terms in this topic
Consumer Contract
A machine-readable record of exactly which parts of a provider's response one consumer relies on, generated from that consumer's own tests.
patternConsumer-Driven Contract
A machine-checkable expectation written by the consumer of an API and verified against the provider's build, catching integration breaks without a sh…
metricContract Coverage Gap
The share of a provider's response that a consumer's code reads but its contract never asserts on - the exact surface a provider can delete while eve…
Neighbouring topics
Testing & Quality Architecture
General material on designing a testing strategy as an architectural concern.
Test Architecture Strategy
Choosing what to verify where, given the failure modes that actually occur.
Test Pyramid Shapes
Pyramid, trophy and honeycomb, and the system properties that justify each shape.
Integration Test Boundaries
What sits inside a test's boundary, what is faked, and the confidence that follows.
Contract Testing at Scale
Keeping dozens of services compatible without an environment that runs all of them.
Test Data Management
Realistic data without copying production personal data into a weaker environment.
Synthetic Data
Generating data with the shape and edge cases of the real thing, and where it misleads.
Environment Parity
The differences between staging and production that decide which bugs survive to release.
Service Virtualisation
Standing in for a dependency you cannot call, and keeping the stand-in honest.
End-to-End Test Economics
Why broad end-to-end suites get slow, flaky and abandoned, and what to keep.
Non-Functional Test Strategy
Testing availability, latency, security and recovery rather than only behaviour.
Performance Test Design
Workload models, warm-up, think time, and the distribution the average hides.
Chaos as a Test
Fault injection with a hypothesis, a blast radius and an abort condition.
Security Testing in the Pipeline
SAST, DAST, dependency and secret scanning, and what to do with the findings.
Accessibility Testing
Automated checks, their ceiling, and the manual testing that has to sit above it.
Mutation Testing
Measuring whether tests would actually notice a defect, not just cover a line.
Flaky Test Management
Quarantine, detection, and the trust a suite loses once red stops meaning broken.
Testing in Production
Synthetic transactions, dark launches and shadow traffic, done deliberately and safely.
Quality Gates
Thresholds that block a release, who may override them, and how they decay.