Practise the standard verbs for verifying contracts and capturing consumer expectations.
0 / 5 completed
1 / 5
Fill in: 'We ___ contracts between services to catch breaking changes early.'
We 'verify contracts' — the standard collocation in contract testing. 'Prove', 'confirm' and 'check up' are less precise or awkward in this technical context.
2 / 5
Fill in: 'Consumer-driven tests ___ expectations before the provider changes its schema.'
We 'capture expectations' — the standard collocation for recording what a consumer relies on. 'Grab', 'catch' and 'seize' are informal and not idiomatic here.
3 / 5
Fill in: 'The pipeline will ___ the contract against the latest provider build.'
We 'validate the contract' — the standard testing collocation. 'Approve', 'pass' and 'clear' are outcomes, not the verb for running the check itself.
4 / 5
Fill in: 'Teams ___ contracts in a shared broker so both sides stay in sync.'
We 'publish contracts' — the standard collocation for sharing them via a broker. 'Print', 'post up' and 'file' are not idiomatic for this workflow.
5 / 5
Fill in: 'A broken contract should ___ the build before it reaches production.'
We 'fail the build' — the standard CI collocation for a blocking test failure. 'Stop', 'halt' and 'kill' are less idiomatic as the standard term used in pipelines.