Uploaded image for project: 'SonarQube'
  1. SonarQube
  2. SONAR-1455

0% code coverage reported with maven-surefire-plugin 2.5

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Won't Fix
    • Affects Version/s: 2.0.1
    • Fix Version/s: None
    • Component/s: Maven Plugin
    • Labels:
      None
    • Environment:
      Windows XP 2002 SP 3

      Description

      I'm using maven-surefire-plugin (2.5) and cobertura-maven-plugin (2.3). When I run "mvn clean sonar:sonar" at the command line I can see that unit tests are run successfully, but in the Sonar dashboard the coverage is reported as 0%. If I remove the maven-surefire-plugin from my pom and try again, the Sonar dashboard displays the expected non-zero amount of code coverage. This is happening with Sonar 2.0.1, but it also was a problem with Sonar 1.11.1.

        Activity

        Hide
        freddy.mallet Freddy Mallet added a comment -

        Hi Matthew, we do need this target/sonar/sonar-pom.xml file to figure out what happens and this file is always generated by Sonar in the target directory of each Maven project/module.

        Thanks

        Show
        freddy.mallet Freddy Mallet added a comment - Hi Matthew, we do need this target/sonar/sonar-pom.xml file to figure out what happens and this file is always generated by Sonar in the target directory of each Maven project/module. Thanks
        Hide
        commissarmatt Matthew Shostak added a comment -

        Is it possible that the lack of such files is symptomatic of a problem?

        Show
        commissarmatt Matthew Shostak added a comment - Is it possible that the lack of such files is symptomatic of a problem?
        Hide
        freddy.mallet Freddy Mallet added a comment -

        Hi Matthew, according to your first description, when you remove the maven-surefire-plugin section from your pom, the problem vanishes. Could you provide the content of this section ? thanks !

        Show
        freddy.mallet Freddy Mallet added a comment - Hi Matthew, according to your first description, when you remove the maven-surefire-plugin section from your pom, the problem vanishes. Could you provide the content of this section ? thanks !
        Hide
        commissarmatt Matthew Shostak added a comment -

        Freddy, today we discovered that if <forkMode>never</forkMode> for the maven-surefire-plugin, we got zero percent coverage reported, even though tests ran. However, if we changed it to <<forkMode>pertest</forkMode>, then Sonar reported the code coverage numbers we were expecting. Similarly for the default (once), the code coverage numbers are what we expect. So it seems to be only with the forkMode set to never that we experience a problem.

        ,

        Show
        commissarmatt Matthew Shostak added a comment - Freddy, today we discovered that if <forkMode>never</forkMode> for the maven-surefire-plugin, we got zero percent coverage reported, even though tests ran. However, if we changed it to <<forkMode>pertest</forkMode>, then Sonar reported the code coverage numbers we were expecting. Similarly for the default (once), the code coverage numbers are what we expect. So it seems to be only with the forkMode set to never that we experience a problem. ,
        Hide
        freddy.mallet Freddy Mallet added a comment -

        Thanks Matthew, I've added a new section in the Sonar FAQ. I'm going to close "won't fix" this issue as nothing can be done on Sonar side except referencing this Maven Cobertura plugin's behavior.

        Show
        freddy.mallet Freddy Mallet added a comment - Thanks Matthew, I've added a new section in the Sonar FAQ . I'm going to close "won't fix" this issue as nothing can be done on Sonar side except referencing this Maven Cobertura plugin's behavior.

          People

          • Assignee:
            freddy.mallet Freddy Mallet
            Reporter:
            commissarmatt Matthew Shostak
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: