For every new feature, developers should ___ a test that proves it works.
To write a test means to create automated code that verifies behaviour. Write is the standard collocation, as in "write unit tests" and "test-writing." Make, do, and build are vaguer and less idiomatic for individual tests. Developers say "write a test for that edge case," so write a test is the precise, professional collocation for producing the automated checks that guard against regressions in a codebase.
2 / 5
To isolate the unit under test, you ___ the external database call.
To mock a dependency means to replace it with a controlled stand-in during testing. Mock is the precise term, behind "mock objects" and libraries like Mockito and Jest mocks. Fake out, trick, and fool are informal and imprecise. Developers "mock the API client," so mock the database call is the correct collocation for substituting a simulated component so a test runs fast and deterministically without real external systems.
3 / 5
Each test must ___ that the result equals the expected value.
To assert means to declare a condition that must be true for a test to pass. Assert is the precise term, behind "assertions" and methods like assertEqual. Claim, state, and declare are general and not the testing keyword. Developers "assert the expected output," so assert that the result is correct is the correct collocation for the step where a test verifies the code produced the right value.
4 / 5
Before merging, the CI server will ___ the full test suite.
To run a suite means to execute a collection of tests together. Run is the standard collocation, as in "run the tests" and "test runner." Play, drive, and operate are not idiomatic for tests. CI pipelines "run the test suite on every commit," so run the suite is the precise, professional collocation for executing all automated checks to confirm the codebase still behaves correctly.
5 / 5
A failing test will ___ the merge so broken code never reaches the main branch.
To gate the merge means to require passing checks before code can be merged. Gate is the precise term, behind "merge gates" and "required status checks." Lock, shut, and bar are general and not the fixed CI phrase. Teams configure "gates that block merging on test failure," so gate the merge is the correct collocation for enforcing that only verified changes enter the main branch.