coverage-guide

JaCoCo coverage is configured in your Gradle build script to measure line, branch, and method coverage across unit and integration tests. Add the JaCoCo plugin, configure coverage goals, and run gradle test or gradle check to generate HTML reports showing which code paths your tests execute.

Coverage targets set minimum thresholds—typically 70–80% for line coverage, lower for branch coverage—that your build enforces. Define these targets in your Gradle configuration to fail builds that fall short, ensuring consistent test quality across your Spring and Kotlin codebase.

Exclude patterns in JaCoCo configuration let you skip generated code, exceptions, or getters from coverage metrics. Apply exclusion rules in Gradle to focus reports on business logic and reduce noise in coverage analysis for Spring projects.

Yes. JaCoCo generates machine-readable reports that CI systems consume to track coverage trends, block merges below thresholds, or publish metrics. Configure your CI pipeline to run gradle check and parse the coverage output alongside test results.

Line coverage counts executed statements; branch coverage measures conditional paths taken; method coverage tracks which functions ran. JaCoCo reports all three to give you layered visibility into test completeness—line coverage alone misses untested branches.

Gradle tasks like integrationTest run a separate test suite; JaCoCo aggregates coverage from both. Configure distinct test sources and coverage reports to distinguish unit and integration test quality, then merge results in CI for a complete picture.