Coverage thresholds in JUnit - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

JUnit Coverage Threshold Failure Output

Given the following JUnit test coverage configuration, what will be the test execution result if the coverage is 74% for branch coverage?

JUnit

jacoco {
  toolVersion = "0.8.8"
  reports {
    xml.required.set(true)
    html.required.set(true)
  }
  coverageVerification {
    violationRules {
      rule {
        limit {
          counter = 'BRANCH'
          value = 'COVERED_RATIO'
          minimum = '0.75'
        }
      }
    }
  }
}

A Test execution passes but with a warning about coverage.

B Test execution passes successfully with no errors.

C Test execution is skipped because coverage is below threshold.

D Test execution fails due to branch coverage below 75%.

💡 Hint

Coverage verification rules enforce minimum coverage thresholds strictly.

The coverageVerification rule requires branch coverage to be at least 75%. Since actual coverage is 74%, the build fails.

❓ assertion

intermediate

Assertion on Coverage Percentage in JUnit Test Report

Which assertion correctly verifies that the line coverage percentage is at least 80% in a JUnit test report parsed as a float variable named coverageLinePercent?

A assertFalse(coverageLinePercent < 80.0);

B assertEquals(coverageLinePercent, 80.0);

C assertTrue(coverageLinePercent >= 80.0);

D assertNotNull(coverageLinePercent > 80.0);

💡 Hint

Use an assertion that checks a condition is true for coverage threshold.

assertTrue with condition coverageLinePercent >= 80.0 correctly asserts coverage meets or exceeds 80%.

🔧 Debug

advanced

Debugging Coverage Threshold Failure in JUnit

A JUnit test suite fails with a coverage threshold violation error, but the reported coverage is 85%. What is the most likely cause?

A The coverage report file is missing or corrupted, causing a false failure.

B The coverage threshold is set higher than 85%, causing failure.

C The test suite has syntax errors unrelated to coverage.

D JUnit does not support coverage thresholds, so the error is invalid.

💡 Hint

Check the configured minimum coverage value in the build tool.

If the threshold is set above 85%, coverage at 85% will fail the check.

❓ framework

advanced

Configuring Coverage Thresholds in JUnit with JaCoCo

Which snippet correctly configures JaCoCo in a Gradle build to fail the build if instruction coverage is below 90%?

A

jacocoTestCoverageVerification {
  violationRules {
    rule {
      limit {
        counter = 'INSTRUCTION'
        value = 'COVERED_RATIO'
        minimum = '0.9'
      }
    }
  }
}

B

jacocoTestCoverageVerification {
  violationRules {
    rule {
      limit {
        counter = 'INSTRUCTION'
        value = 'COVERED_RATIO'
        minimum = 0.9
      }
    }
  }
}

C

jacocoTestCoverageVerification {
  violationRules {
    rule {
      limit {
        counter = 'INSTRUCTION'
        value = 'COVERED_PERCENTAGE'
        minimum = '90'
      }
    }
  }
}

D

jacocoTestCoverageVerification {
  violationRules {
    rule {
      limit {
        counter = 'INSTRUCTION'
        value = 'COVERED_RATIO'
        minimum = 90
      }
    }
  }
}

💡 Hint

Minimum must be a string representing a decimal ratio between 0 and 1.

JaCoCo expects minimum coverage as a string decimal like '0.9' for 90%.

🧠 Conceptual

expert

Impact of Coverage Thresholds on Continuous Integration

Which statement best describes the impact of strict coverage thresholds in a CI pipeline using JUnit and JaCoCo?

A Strict thresholds ensure high code quality but may cause frequent build failures requiring quick fixes.

B Strict thresholds have no impact on build stability or developer workflow.

C Strict thresholds automatically fix coverage gaps without developer intervention.

D Strict thresholds reduce test execution time by skipping low coverage tests.

💡 Hint

Consider how coverage enforcement affects build success and developer actions.

Strict coverage thresholds enforce quality but can cause builds to fail if coverage drops, prompting developers to fix tests or code.

Practice

1. What is the main purpose of setting coverage thresholds in JUnit testing?

easy

A. To automatically fix bugs in the code

B. To speed up test execution time

C. To ensure a minimum percentage of code is tested

D. To generate user interface reports

Solution

1. Step 1: Understand coverage thresholds

   Coverage thresholds define the minimum amount of code that must be tested to pass.

2. Step 2: Identify the main goal

   The goal is to keep tests thorough by enforcing minimum test coverage.

3. Final Answer:

   To ensure a minimum percentage of code is tested -> Option C

4. Quick Check:

   Coverage thresholds = minimum tested code [OK]

Hint: Coverage thresholds set minimum tested code percentage [OK]

Common Mistakes:

• Thinking thresholds speed up tests
• Believing thresholds fix bugs automatically
• Confusing thresholds with report generation

2. Which of the following is the correct way to set a line coverage threshold of 80% using JaCoCo in a Maven pom.xml?

easy

A. <rule><limit><counter>LINE</counter><value>COVEREDRATIO</value><minimum>0.8</minimum></limit></rule>

B. <rule><limit><counter>LINE</counter><value>MISSEDCOUNT</value><maximum>0.8</maximum></limit></rule>

C. <rule><limit><counter>BRANCH</counter><value>COVEREDRATIO</value><minimum>80</minimum></limit></rule>

D. <rule><limit><counter>LINE</counter><value>COVEREDCOUNT</value><minimum>0.8</minimum></limit></rule>

Solution

1. Step 1: Identify correct counter and value

   For line coverage, the counter is LINE and the value to check coverage ratio is COVEREDRATIO.

2. Step 2: Check threshold value format

   Minimum coverage is set as a decimal ratio (0.8 for 80%).

3. Final Answer:

   Rule with LINE counter, COVEREDRATIO value, and minimum 0.8 -> Option A

4. Quick Check:

   Line coverage threshold = 0.8 COVEREDRATIO [OK]

Hint: Use LINE + COVEREDRATIO + minimum 0.8 for 80% threshold [OK]

Common Mistakes:

• Using MISSEDCOUNT instead of COVEREDRATIO
• Setting minimum as 80 instead of 0.8
• Confusing BRANCH counter with LINE

3. Given the following JaCoCo coverage report snippet:

{"LINE": {"covered": 40, "missed": 10}}

What is the line coverage ratio, and does it meet a threshold of 85%?

medium

A. Coverage is 75%, which does not meet the 85% threshold

B. Coverage is 75%, which meets the 85% threshold

C. Coverage is 80%, which meets the 85% threshold

D. Coverage is 80%, which does not meet the 85% threshold

Solution

1. Step 1: Calculate coverage ratio

   Total lines = covered + missed = 40 + 10 = 50. Coverage ratio = 40 / 50 = 0.8 or 80%.

2. Step 2: Compare with threshold

   Threshold is 85%, coverage is 80%, so coverage does not meet threshold.

3. Final Answer:

   Coverage is 80%, which does not meet the 85% threshold -> Option D

4. Quick Check:

   40/50 = 0.8 < 0.85 [OK]

Hint: Divide covered by total lines, compare to threshold [OK]

Common Mistakes:

• Adding covered and missed incorrectly
• Confusing coverage percentage with missed percentage
• Assuming 80% meets 85% threshold

4. You set a branch coverage threshold of 90% in your JaCoCo config, but the build passes even when coverage is 85%. What is the most likely cause?

medium

A. The JaCoCo plugin is not configured to fail the build on threshold violation

B. The threshold value is set as maximum instead of minimum

C. Branch coverage cannot be enforced with JaCoCo

D. The threshold is set on LINE coverage, not BRANCH coverage

Solution

1. Step 1: Understand threshold enforcement

   Thresholds require configuration to fail the build if coverage is below minimum.

2. Step 2: Identify common misconfiguration

   If the build passes despite low coverage, likely the fail-on-violation setting is missing or disabled.

3. Final Answer:

   JaCoCo plugin not configured to fail build on threshold violation -> Option A

4. Quick Check:

   Fail build setting missing = threshold ignored [OK]

Hint: Fail build must be enabled to enforce coverage thresholds [OK]

Common Mistakes:

• Confusing LINE and BRANCH counters
• Setting maximum instead of minimum threshold
• Believing branch coverage can't be enforced

5. You want to enforce multiple coverage thresholds in your JUnit project using JaCoCo: 85% line coverage and 75% branch coverage. Which configuration snippet correctly enforces both thresholds?

hard

A. <rules>
<rule><limit><counter>LINE</counter><value>COVEREDCOUNT</value><minimum>85</minimum></limit></rule>
<rule><limit><counter>BRANCH</counter><value>COVEREDCOUNT</value><minimum>75</minimum></limit></rule>
</rules>

B. <rules>
<rule>
<limits>
<limit><counter>LINE</counter><value>COVEREDRATIO</value><minimum>0.85</minimum></limit>
<limit><counter>BRANCH</counter><value>COVEREDRATIO</value><minimum>0.75</minimum></limit>
</limits>
</rule>
</rules>

C. <rules>
<rule><limit><counter>LINE</counter><value>MISSEDCOUNT</value><maximum>0.15</maximum></limit></rule>
<rule><limit><counter>BRANCH</counter><value>MISSEDCOUNT</value><maximum>0.25</maximum></limit></rule>
</rules>

D. <rules>
<rule><limit><counter>LINE</counter><value>COVEREDRATIO</value><minimum>0.75</minimum></limit></rule>
<rule><limit><counter>BRANCH</counter><value>COVEREDRATIO</value><minimum>0.85</minimum></limit></rule>
</rules>

Solution

1. Step 1: Check counters and values

   Use LINE and BRANCH counters with COVEREDRATIO values for coverage percentages.

2. Step 2: Verify minimum thresholds and structure

   Minimum values must be decimals (0.85 and 0.75) inside a single rule with multiple limits.

3. Final Answer:

   Rules with LINE and BRANCH counters, COVEREDRATIO values, minimum 0.85 and 0.75 -> Option B

4. Quick Check:

   Multiple limits in one rule with correct decimals [OK]

Hint: Use multiple limits inside one rule with decimals for thresholds [OK]

Common Mistakes:

• Using COVEREDCOUNT with integer minimums instead of decimals
• Swapping threshold values between LINE and BRANCH
• Splitting limits into separate rules incorrectly