Search code examples
gradlesonarqubejacocomulti-module

Cross-module code coverage with jacoco and gradle multi-module project

We use gradle 3.3 and jacoco tool verson 0.7.6.201602180812. We have a gradle multi-project like this:

  • parent
    • prod1
    • prod2
    • prod3
    • int-test

We use unit-tests testing the project sources and jacoco on all child-projects producing test.exec files. We have additional integration-tests in the int-test project adding jacoco results to the test-exec in the int-test project. We use sonarqube gradle plugin (2.2.1) on the parent project to collect everything for a SonarQube server v6.2.

Everything runs fine with tests that test sources in their own project: The code coverage is measured in the jacoco reports as well as on SonarQube.

Only the integration test (int-test project) coverage for the sources in the prod-projects (single process) is not measured neither in the coverage report in the project with the test nor in the project with the class.

Probably one needs to combine the coverage data on the top level project somehow - does anyone know how to do that? At best with SonarQube still showing the coverage on single module level as well.

EDIT Here is a small test project: https://github.com/MichaelZett/coveragetest Running
'build smokeTest sonarqube' leads to:

  • Run of all tests
  • producing jacoco/test.exec and test-results/test/... files in all child projects
  • parsing of these in sonarqube
  • correct measurement of coverage for tests that test sources in their own projects
  • missing coverage for tests that test sources in another project
Solution

  • Speaking about SonarQube: you can get aggregated report by using same location for jacoco.exec across all modules. Make sure that file is removed before build and appended in all modules.

    Speaking solely about Gradle: have a look on