Practice the vocabulary of consumer-driven contract testing with Pact: consumer tests, provider verification, and can-i-deploy.
0 / 5 completed
1 / 5
In Pact contract testing, who 'defines the expectations' in a consumer-driven contract?
In consumer-driven contracts, the consumer writes tests that capture its expectations of the provider's API. These expectations become the contract the provider must satisfy.
2 / 5
What happens during 'provider verification' in a Pact workflow?
Provider verification is when the provider side runs the published contract against its actual implementation. If all interactions pass, the provider is verified against that consumer version.
3 / 5
A team says 'we use can-i-deploy before every production release'. What does can-i-deploy check?
can-i-deploy is a Pact CLI command that queries the Pact Broker to confirm that the specific versions of consumer and provider about to be deployed are compatible (have a passing verification).
4 / 5
What is the 'Pact Broker' in a contract testing workflow?
The Pact Broker is a shared repository for contracts (pacts) and verification results. It enables consumers and providers to publish and retrieve contracts independently without sharing code.
5 / 5
A developer says 'the consumer test is green but provider verification failed'. What does this mean?
When provider verification fails, it means the provider's real implementation returns something that doesn't match what the consumer expected — a breaking change or divergence that must be resolved before deployment.