Skip to content
It provides the ability to feed SonarQube with code coverage data coming from Atlassian Clover
Java Makefile Groovy Dockerfile
Branch: master
Clone or download
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github/ISSUE_TEMPLATE Update issue templates (#28) Feb 5, 2019
its Use new coverage API (#34) Sep 27, 2019
src Use new coverage API (#34) Sep 27, 2019
.dockerignore Use new coverage API (#34) Sep 27, 2019
.gitignore Use new coverage API (#34) Sep 27, 2019
.travis.yml chore(CI/CD): prepare and automate release Sep 27, 2019
CODE_OF_CONDUCT docs: add code of conduct (#27) Feb 5, 2019
Dockerfile Use new coverage API (#34) Sep 27, 2019
LICENSE docs: add LICENSE (#26) Feb 5, 2019
Makefile fix(CI/CD): missing BINTRAY credentials Sep 27, 2019
README.md
contributing.md Use new coverage API (#34) Sep 27, 2019
pom.xml fix(CI/CD): add missing distribution management Sep 27, 2019
travis.settings.xml fix(CI/CD): add missing distribution management Sep 27, 2019

README.md

Sonar Clover

Build Status

Description / Features

It provides the ability to feed SonarQube with code coverage data coming from Atlassian Clover or it's new open source version: OpenClover.

Usage

To display code coverage data:

  1. Prior to the SonarQube analysis, execute your unit tests and generate the Clover report.

  2. Import this report while running the SonarQube analysis by setting the sonar.clover.reportPath (using prior version to sonarQube version 6) or sonar.coverageReportPaths (sonarQube v7 or higher, FYI with this version, only the xml format is supported) property to the path to the Clover report. The path may be absolute or relative to the project base directory.

You can’t perform that action at this time.