Bird
Raised Fist0
JUnittesting~15 mins

Coverage reports in JUnit - Build an Automation Script

Choose your learning style10 modes available
Generate and verify code coverage report for Calculator class
Preconditions (3)
Step 1: Run the CalculatorTest JUnit test class using the build tool
Step 2: Locate the generated JaCoCo coverage report in the target or build directory
Step 3: Open the coverage report HTML file in a browser
Step 4: Verify that the coverage report shows 100% coverage for Calculator class methods add and subtract
โœ… Expected Result: The coverage report shows 100% line and branch coverage for the Calculator class methods tested
Automation Requirements - JUnit 5 with JaCoCo
Assertions Needed:
Test methods execute without errors
Coverage report file exists after test run
Coverage report indicates 100% coverage for Calculator class methods
Best Practices:
Use JUnit 5 annotations and assertions
Configure JaCoCo plugin properly in build tool
Run tests and generate coverage report in a single build command
Verify coverage report file existence programmatically
Do not hardcode file paths; use relative paths or build tool properties
Automated Solution
JUnit
import static org.junit.jupiter.api.Assertions.*;
import org.junit.jupiter.api.Test;
import java.io.File;

public class CalculatorTest {

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

    @Test
    public void testSubtract() {
        Calculator calc = new Calculator();
        assertEquals(1, calc.subtract(3, 2));
        assertEquals(5, calc.subtract(2, -3));
    }

    @Test
    public void testCoverageReportExists() {
        // Assuming Maven default target directory and JaCoCo report path
        File report = new File("target/site/jacoco/index.html");
        assertTrue(report.exists(), "Coverage report should exist after tests run");
    }
}

// Sample Calculator class
class Calculator {
    public int add(int a, int b) {
        return a + b;
    }

    public int subtract(int a, int b) {
        return a - b;
    }
}

/*
Note: To generate coverage report, run:
  mvn clean test jacoco:report

Then open target/site/jacoco/index.html to verify coverage manually.
*/

The test class CalculatorTest contains three tests:

  • testAdd() verifies the add method with two cases.
  • testSubtract() verifies the subtract method with two cases.
  • testCoverageReportExists() checks if the JaCoCo coverage report file exists after running tests.

The Calculator class is simple with two methods to test.

Running mvn clean test jacoco:report will execute tests and generate the coverage report.

The coverage report file existence is asserted programmatically to confirm report generation.

Manual verification of coverage percentage is recommended by opening the HTML report in a browser.

Common Mistakes - 4 Pitfalls
Not configuring JaCoCo plugin in the build tool
Hardcoding absolute file paths for coverage report
Not running the coverage report generation goal after tests
Not asserting coverage report existence in automation
Bonus Challenge

Now add data-driven testing for Calculator add method with 3 different input pairs

Show Hint

Practice

(1/5)
1. What is the main purpose of a coverage report in JUnit testing?
easy
A. To show which parts of the code were executed during tests
B. To list all test cases in the project
C. To measure the speed of test execution
D. To generate test data automatically

Solution

  1. Step 1: Understand coverage report purpose

    A coverage report shows which lines or branches of code were run during testing.
  2. Step 2: Compare options to definition

    Only To show which parts of the code were executed during tests matches this purpose; others describe unrelated features.
  3. Final Answer:

    To show which parts of the code were executed during tests -> Option A
  4. Quick Check:

    Coverage report = executed code lines [OK]
Hint: Coverage reports highlight tested code lines quickly [OK]
Common Mistakes:
  • Confusing coverage with test case listing
  • Thinking coverage measures test speed
  • Assuming coverage generates test data
2. Which tool is commonly used with JUnit to generate coverage reports?
easy
A. JaCoCo
B. JUnitParams
C. Mockito
D. Selenium

Solution

  1. Step 1: Identify coverage tools for JUnit

    JaCoCo is a popular Java code coverage tool that integrates with JUnit.
  2. Step 2: Eliminate unrelated tools

    Selenium is for UI testing, Mockito for mocking, JUnitParams for parameterized tests, not coverage.
  3. Final Answer:

    JaCoCo -> Option A
  4. Quick Check:

    Coverage tool with JUnit = JaCoCo [OK]
Hint: JaCoCo is the go-to coverage tool for Java tests [OK]
Common Mistakes:
  • Confusing Selenium with coverage tools
  • Mixing mocking frameworks with coverage
  • Assuming JUnitParams generates coverage
3. Given this JaCoCo coverage summary:
Lines covered: 80
Lines missed: 20

What is the coverage percentage?
medium
A. 100%
B. 20%
C. 80%
D. 60%

Solution

  1. Step 1: Calculate total lines

    Total lines = covered + missed = 80 + 20 = 100 lines.
  2. Step 2: Calculate coverage percentage

    Coverage % = (covered / total) * 100 = (80 / 100) * 100 = 80%.
  3. Final Answer:

    80% -> Option C
  4. Quick Check:

    80 covered of 100 total = 80% [OK]
Hint: Coverage % = covered lines รท total lines x 100 [OK]
Common Mistakes:
  • Using missed lines as coverage
  • Forgetting to add covered and missed for total
  • Mixing up numerator and denominator
4. You ran tests with JaCoCo but the coverage report shows 0% coverage. What is the most likely cause?
medium
A. Tests did not execute any code
B. JaCoCo was not properly attached to the test run
C. All tests passed successfully
D. The source code is empty

Solution

  1. Step 1: Analyze 0% coverage meaning

    0% coverage means no code was recorded as executed during tests.
  2. Step 2: Identify common causes

    If tests ran but coverage is zero, JaCoCo likely was not attached or configured correctly.
  3. Final Answer:

    JaCoCo was not properly attached to the test run -> Option B
  4. Quick Check:

    0% coverage usually means missing JaCoCo setup [OK]
Hint: Check JaCoCo setup if coverage is zero [OK]
Common Mistakes:
  • Assuming tests passed means coverage is full
  • Thinking empty source code is common
  • Ignoring JaCoCo configuration errors
5. You want to improve your test coverage report by including branch coverage in JaCoCo. Which configuration change is needed?
hard
A. Increase the number of test classes
B. Add @BranchCoverage annotation to test methods
C. Use a different testing framework instead of JUnit
D. Enable branchCoverage option in JaCoCo plugin settings

Solution

  1. Step 1: Understand branch coverage

    Branch coverage measures if all decision branches (like if/else) are tested.
  2. Step 2: Configure JaCoCo for branch coverage

    JaCoCo supports branch coverage via plugin settings; enabling branchCoverage activates it.
  3. Step 3: Eliminate incorrect options

    No annotation @BranchCoverage exists; changing framework or test count doesn't enable branch coverage reporting.
  4. Final Answer:

    Enable branchCoverage option in JaCoCo plugin settings -> Option D
  5. Quick Check:

    Branch coverage = enable in JaCoCo config [OK]
Hint: Enable branchCoverage in JaCoCo config to track branches [OK]
Common Mistakes:
  • Looking for annotations to enable coverage
  • Thinking more tests auto-enable branch coverage
  • Switching frameworks unnecessarily
Recommended

Ready to prove it?

Pass the test and this pattern moves unknown strong while earning +1 Grip toward your certificate.

10 questions~5 mineasy hard