Skip to main content
Automation

What Is Code Coverage?

Code coverage is a metric that measures which lines, branches, or paths of source code are executed by automated tests, typically expressed as a percentage and generated by instrumentation tools.

Start a Free Mock Interview

Free to start · 7-day trial on paid plans

In Depth

Code coverage tools instrument source code (or bytecode) to track which lines execute during test runs. Line coverage reports the percentage of source lines executed. Branch coverage checks whether both sides of every conditional (if/else, switch cases, ternary operators) are exercised. Path coverage, the most thorough, tracks every unique execution path through a function, though it is often impractical for complex code due to combinatorial explosion.

Popular tools include Istanbul/NYC for JavaScript/TypeScript, JaCoCo for Java, coverage.py for Python, and SimpleCov for Ruby. Most CI systems can integrate coverage reports and fail builds that drop below a configured threshold. Some teams use coverage-gating on pull requests to ensure new code is covered.

The key insight for practitioners is that coverage measures execution, not verification. A test that calls a function without asserting its return value adds line coverage but no quality assurance. Coverage is most valuable as a gap-finding tool: low-coverage areas indicate untested code that might harbor bugs. It should guide testing priorities, not define quality.

Why Interviewers Ask About This

Interviewers ask about code coverage to test whether you understand the distinction between measuring execution and verifying correctness. They want nuanced discussion, not just naming tools.

Example Scenario

A PR adds a helper function with three branches (success, validation error, network error). The coverage report shows 67% branch coverage because no test triggers the network-error path. The reviewer requests an additional test that simulates a network failure, raising branch coverage to 100% for that function.

Interview Tip

Name specific coverage types (line, branch, path) and tools for your language. Discuss the difference between "covered" and "tested" and how you use coverage reports in code reviews.

Related Terms

Explore related glossary terms to deepen your understanding.

Test CoverageTest coverage is a metric that measures the extent to which a test suite exercises the application, expressed as a percentage of code lines, branches, requirements, or features verified by tests.
Mutation TestingMutation testing is a technique that evaluates the quality of a test suite by introducing small, deliberate changes (mutants) to the source code and checking whether the tests detect and fail on those changes.
Test PyramidThe Test Pyramid is a testing strategy that prescribes a large base of fast, isolated unit tests, a smaller middle layer of integration tests, and a thin top layer of end-to-end tests.
Mocking vs StubbingMocking and stubbing are both techniques for replacing real dependencies with test doubles, but stubs provide canned responses to calls while mocks additionally verify that specific interactions occurred.
Continuous TestingContinuous testing is the practice of executing automated tests at every stage of the CI/CD pipeline, providing immediate feedback on the risk level of each code change as it moves toward production.

Related Resources

Dive deeper with these related interview prep pages.

SDET Interview PrepAutomation Testing InterviewJenkins Interview QuestionsGitHub Actions Interview QuestionsTop 20 QA Interview Questions (2026)

Ready to Ace Your QA Interview?

Practice explaining code coverage and other key concepts with our AI interviewer.

Join 1,200+ QA engineers already practicing with AssertHired.

Start Your Free QA Interview

Free to start · 7-day trial on paid plans

Written by Aston Cook, Senior QA EngineerLast updated: March 2026