Home › Software Testing › Software Testing › microservices_cloud_observability › Consumer driven contract testing (e.g., Pact) ve…
Consumer driven contract testing (e.g., Pact) verifies that
AProvider continues to meet consumer expectations
BConsumer code never changes without provider
CBoth consumer and provider use one repository
DBoth consumer and provider use the same OS
Answer & Solution
Correct answer: A. Provider continues to meet consumer expectations
CDCT records consumer expectations as a 'pact' file. The provider runs these contracts in its pipeline; if the provider breaks a consumer contract, the build fails BEFORE the change ships. Catches integration regressions early.
Related questions
A 'red team' in security testing is a group that'Test impact analysis' speeds CI byIn Test Maturity Model integrated (TMMi), Level 2 is'Test pyramid' for microservices typically pushes effort toQuality gates in a deployment pipeline areA test environment management strategy primarily addressesGame days in production resilience testing involveFeature flags enable testing by