Course contentsShow
← Software Engineering
Lesson 590 of 1,93318. Test CoverageFree lesson

Reading Coverage Reports

Interpreting coverage tool output: percentages, highlighted code, and identifying uncovered lines or branches.

Reading Coverage Reports

What you'll learn: How to interpret the output from coverage tools so you can spot exactly which code is tested and which isn't.

Understanding Coverage Tool Output

When you run a coverage tool, it generates a report showing which parts of your code were executed during tests. Think of it like a map that highlights which roads your test "car" drove on and which were never visited.

The Three Main Elements

1. Percentages Coverage reports display percentages for each file and the overall project:

  • 85% line coverage means 85 out of 100 lines were executed
  • Percentages appear at file, module, and project levels
  • Different metrics (line, branch, function) each have their own percentage

2. Highlighted Code Most tools color-code your source files:

  • Green (or covered): Lines executed by at least one test
  • Red (or uncovered): Lines never executed during testing
  • Yellow/Orange: Partially covered branches (one path taken, another missed)

3. Identifying Uncovered Areas

Reports pinpoint specific problems:

  • Uncovered lines: Line numbers shown in red or with 0 hit count
  • Uncovered branches: Conditional statements where only if or only else was tested
  • Uncovered functions: Methods that were never called

Reading the Report

Look for patterns:

  • Low coverage in a file? Might need more tests
  • Red lines in error handling? Edge cases probably untested
  • Yellow branches in conditionals? Missing test cases for different paths

Key Takeaway: Coverage reports use percentages, color-coding, and line numbers to show you exactly what your tests exercise and what they miss—turning invisible test gaps into visible targets for improvement.