File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
The moose likes Testing and the fly likes Cobertura code coverage issue Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Engineering » Testing
Bookmark "Cobertura code coverage issue" Watch "Cobertura code coverage issue" New topic
Author

Cobertura code coverage issue

Miten Morakhia
Greenhorn

Joined: Nov 18, 2011
Posts: 1
Hi there,

We are using sonar in our project. Sonar by default uses cobertura for determining code coverage. My application is divided into multiple projects and each of them having their own pom.xml files. So as I understand, the cobertura stats will also be calculated on per project basis.

My pom.xml has following config
<reporting>
<plugins>
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>cobertura-maven-plugin</artifactId>
<version>2.4</version>
</plugin>

The problem that I am facing is I have a JUnit test class in project A which calls and tests certain classes in project B. However, when I look at the cobertura report for project B, it shows 0% line coverage. Coverage report for project A anyways would not contain the details about project B. Is there some configuration required for getting the correct code coverage?

I suspected it might be due to cobertura instrument details not getting merged correctly hence I tried adding the following in the pom.xml files of project A & B but still the results were no different.

<cobertura-merge>
<fileset dir="${basedir}">
<include name="**/cobertura.ser" />
</fileset>
</cobertura-merge>

In any case, I think Sonar should be smart enough to merge the results. Any specific configuration changes that I might need to make in order to get the correct code coverage figures?
This is important for us because we do not want to lag behind the other teams who are faring much better code coverage. We know that a lot of code has been covered via unit and integration testing classes but don't have the numbers to prove it!

Has anyone faced similar issue in the past?

Thanks,
Miten
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Cobertura code coverage issue
 
Similar Threads
where do i add the reporting tag so that i get the maven test reports generated in surefire reports
Tomcat and Axis2
Could not resolve dependencies for maven project
emma-maven-plugin - filter excludes
Cannot locate the artifact jbossws-native-jaxrpc