Okuzeka
Software Engineering vocabulary · Testing

Test coverage

Meaning in software engineering, with examples

/ˈtest ˌkʌvərɪdʒ/nounCommon term

In software engineering, test coverage means: A measure, often a percentage, of how much of the code is run by automated tests. It shows which parts are tested and which are not.

In Turkish: test kapsamı, kod kapsamı

How it is used

Teams measure, report and increase test coverage, and some CI pipelines fail if it drops below a set limit. Reviewers often point out that high coverage does not guarantee good tests.

Example sentences

  1. Test coverage for the billing module is only 40 percent.

  2. This PR adds tests for the error paths and raises test coverage to 85 percent.

Common collocations

  • increase test coverage
  • code coverage
  • coverage report
  • low test coverage
  • unit testA small automated test that checks one function or class on its own, separate from the database, the network and the rest of the system.
  • integration testA test that checks how several parts of a system work together, for example your code with a real database or another service.
  • test caseOne specific situation you check, with set inputs, steps and an expected result, for example 'logging in with a wrong password shows an error'.
  • CI/CDShort for continuous integration and continuous delivery (or deployment): automatically building and testing every change, then releasing it quickly and safely.

More terms: Testing

Practise with graded reading

Reading at the right level is the fastest way to make new words stick. Pick free English books by level: