Why coverage measures test completeness in JUnit - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

What does code coverage measure in testing?

In software testing, code coverage is used to measure how much of the code is tested. What exactly does code coverage measure?

A The number of bugs found during testing

B The number of tests written for the software

C The time taken to run all tests

D The percentage of code lines executed by tests

💡 Hint

Think about what 'coverage' means in everyday life, like covering a surface.

Code coverage measures how many lines or parts of the code are actually run when tests are executed. It shows how much of the code is 'covered' by tests.

❓ Predict Output

intermediate

JUnit test coverage output interpretation

Given this JUnit test and code, what coverage percentage will be reported?

JUnit

public class Calculator {
    public int add(int a, int b) {
        return a + b;
    }
    public int subtract(int a, int b) {
        return a - b;
    }
}

import static org.junit.jupiter.api.Assertions.*;
import org.junit.jupiter.api.Test;

public class CalculatorTest {
    @Test
    public void testAdd() {
        Calculator calc = new Calculator();
        assertEquals(5, calc.add(2, 3));
    }
}

A 50%

B 100%

C 0%

D 75%

💡 Hint

Only one method is tested out of two.

The test only calls the add method, so only that method's code is executed. The subtract method is not tested, so coverage is 50%.

❓ assertion

advanced

Which assertion best checks test completeness using coverage?

You want to assert that your JUnit tests cover all branches of a method. Which assertion best reflects this completeness?

A assertFalse(coveragePercentage > 0)

B assertTrue(coveragePercentage == 100, "All branches covered")

C assertNotNull(coveragePercentage)

D assertEquals(coveragePercentage, 50)

💡 Hint

Complete coverage means 100% coverage.

To confirm all branches are covered, coverage must be 100%. The assertion checks this exactly.

🔧 Debug

advanced

Why does coverage report less than 100% despite all tests passing?

You have written JUnit tests that pass, but coverage reports only 80%. What is the most likely reason?

A JUnit tests have syntax errors

B Coverage tool is not installed

C Some code branches or lines are not executed by any test

D Tests are running too fast

💡 Hint

Passing tests do not guarantee all code paths run.

Tests may pass but not cover all code paths, so coverage is less than 100%. This shows incomplete test coverage.

❓ framework

expert

How to configure JUnit to measure branch coverage accurately?

Which configuration or tool setup ensures JUnit tests measure branch coverage accurately?

A Use JaCoCo agent with JVM argument and enable branch coverage in report settings

B Use System.out.println statements to track coverage manually

C Run JUnit tests without any coverage tool attached

D Disable assertions in JUnit tests

💡 Hint

Coverage tools need to instrument code to measure branches.

JaCoCo is a popular coverage tool that instruments code at runtime. Enabling branch coverage in its settings ensures accurate measurement of all branches during JUnit test execution.