Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

"No information about coverage per test." from Sonar with Jacoco Ant build

I'm using Ant, Jacoco and Sonar. When I run my build Sonar tells me that "No information about coverage per test." and the Sonar dashboard has my coverage results, but I cannot drill down into them to see the code. However, the HTML report generated by Jacoco does include drill down into the code. This is my coverage task:

    <jacoco:coverage destfile="${coverage.output.file}" >
        <junit printsummary="on" 
            errorProperty="test.failed" 
            failureProperty="test.failed" 
            haltonfailure="yes" 
            fork="true">
            <formatter type="brief" usefile="false" />
            <formatter type="xml" />
            <classpath>
                <path refid="test.build.class.path"/>
                <pathelement location="${test.bin.dir}"/>       
            </classpath>
            <batchtest todir="${results.dir}">
                <fileset dir="${test.bin.dir}">
                    <include name = "**/**/*Test.class"/>
                </fileset>
            </batchtest>
        </junit>
    </jacoco:coverage>  

    <jacoco:report>
        <executiondata>
            <file file="${coverage.output.file}"/>
        </executiondata>
        <structure name="${ant.project.name}">
            <classfiles>
                <fileset dir="${bin.dir}"/>
            </classfiles>
            <sourcefiles encoding="UTF-8">
                <fileset dir="${src.dir}"/>
            </sourcefiles>
        </structure>
        <html destdir="${coverage.results.dir}"/>
    </jacoco:report>
</target>

And my Sonar target looks like this:

<target name="sonar" depends = "run">
    <property name="sonar.jdbc.url" value="..." />
    <property name="sonar.jdbc.username" value="...r" />
    <property name="sonar.jdbc.password" value="..." />

    <property name="sonar.projectKey" value="org.codehaus.sonar:example-java-ant" />
    <property name="sonar.projectName" value="${ant.project.name} (ant)" />
    <property name="sonar.projectVersion" value="1.0" />
    <property name="sonar.language" value="java" />
    <property name="sonar.sources" value="${src.dir}" />
    <property name="sonar.binaries" value="${bin.dir},${test.bin.dir}" />
    <property name="sonar.libraries" value="${lib.dir}/*.jar" />    

    <property name="sonar.dynamicAnalysis" value="reuseReports" />
    <property name="sonar.surefire.reportsPath" value="${results.dir}" />
    <property name="sonar.java.coveragePlugin" value="jacoco" />
    <property name="sonar.jacoco.reportPath" value="${coverage.output.file}" />

    <taskdef uri="antlib:org.sonar.ant" resource="org/sonar/ant/antlib.xml">
         <classpath>         
            <fileset dir="${lib.dir}" includes="sonar-ant-task-2.0.jar"/>
         </classpath>
    </taskdef>   

    <sonar:sonar />     
</target>

Does anyone know what I am missing?

like image 587
Paul Grenyer Avatar asked May 17 '13 18:05

Paul Grenyer


People also ask

What helps get per exam coverage in SonarQube?

SonarQube itself does not calculate coverage. To include coverage results in your analysis, you must set up a third-party coverage tool and configure SonarQube to import the results produced by that tool. Below, you'll find guidelines and resources, as well as language- and tool-specific analysis parameters.

How do I see code coverage in SonarQube?

Viewing the SonarQube report details We can head back to SonarQube at localhost:9000/projects to see the test code coverage report. We can see a reported code coverage of 66.7%.

How does JaCoCo determine coverage?

JaCoCo mainly provides three important metrics: Lines coverage reflects the amount of code that has been exercised based on the number of Java byte code instructions called by the tests. Branches coverage shows the percent of exercised branches in the code, typically related to if/else and switch statements.

Does sonar use JaCoCo?

SonarQube is used in integration with JaCoCo, a free code coverage library for Java.


2 Answers

It looks like you haven't set the 'sonar.tests' property to tell Sonar where to find the source code of your unit tests. See http://docs.sonarqube.org/display/SONAR/Analysis+Parameters.

David RACODON | SonarSource

like image 187
David RACODON - QA Consultant Avatar answered Sep 30 '22 14:09

David RACODON - QA Consultant


The sonar.test property should be set to the test-classes. We have the following in our maven pom. For ANT you do something similar:

    <profile>
        <id>sonarprofile</id>
        <activation>
            <activeByDefault>true</activeByDefault>
        </activation>
        <properties>
            <sonar.host.url>....our host..../sonar.host.url>
            <sonar.projectKey>....our key....</sonar.projectKey>
            <sonar.projectName>${project.artifactId}</sonar.projectName>
            <sonar.projectVersion>${project.version}</sonar.projectVersion>
            <sonar.language>java</sonar.language>
            <sonar.sources>src/main/java</sonar.sources>
            <!-- sonar.tests>target/test-classes</sonar.tests -->
            <!-- that is the default location for Maven projects and -->
            <!-- this parameter can't actually be set in that case -->
            <sonar.scm.provider>git</sonar.scm.provider>
            <sonar.login>${SONAR_LOGIN}</sonar.login>
            <sonar.dynamicAnalysis>reuseReports</sonar.dynamicAnalysis>
            <sonar.java.coveragePlugin>jacoco</sonar.java.coveragePlugin>
            <sonar.jacoco.reportPath>${basedir}/target/coverage-reports/jacoco-unit.exec</sonar.jacoco.reportPath>
        </properties>
    </profile>

Incidently there are some other properties being used in this:

  • I've generated a SONAR token through my sonar user rather than use login and password
  • JaCoCo coverage is being generated separately using the jacoco-maven-plugin and the sonar.jacoco.reportPath is a property used in that plugin.

David Racodon's answer (https://stackoverflow.com/a/16645108/1019307) was once correct but in mid-2014 SonarQube stopped executing the tests as part of the sonar execution (http://www.sonarqube.org/unit-test-execution-in-sonarqube/). Hence why pointing to the test source no longer works.

like image 43
HankCa Avatar answered Sep 30 '22 12:09

HankCa