I must run 'mvn cobertura:cobertura' twice to get a valid coverage report.

I have the same problem. Basically, 'mvn clean cobertura:cobertura' gives 0% coverage on all tests, 'mvn clean cobertura:cobertura cobertura:cobertura' works correctly. This seems the same as MCOBERTURA-25, however using surefire-2.3doesn't help, see the last remarks there.

I have tried moving back to 1.7 and it still does not work. AND we cannot run it twice because that does not work either. It does not work because we have 2 projects which need cobertura reports and both are run from a parent pom. Running mvn cobertura:cobertura twice from the parent does not work! We literally have to do a changedir (cd) to each project and run it twice – which defeats the purpose of a build environment. We need some kind of fix for this ASAP. C'mon, it can't be that hard to fix. If it is, then Cobertura really has something wrong architecturally.

I had the same above problem and the following workaround worked for me:

– I set the configuration on the maven-surefire-plugin to start in forkmode.
<configuration>
<forkMode>once</forkMode>
</configuration>

Can somebody verify this?

Thanks,
Giri

@Giridhar:
In my case, this workaround doesn't really work. Now, the report indeed is generated with the first run, but it doesn't show all classes and those which are shown got all a test-coverage of 100%, which is wrong.

Regards,
Claude

The 100% issue was solved in version 2.2, please try that version.

@Claude
My workaround isn't right. As per Dennis, this works for me with version 2.2.

Thanks,
Giri

Just for reference: I can confirm that this works with cobertura-maven-plugin-2.2 if I set forkMode = once (the default). See http://www.nabble.com/surefire-forkMode-setting-td22863160.html.

Hello

Also with version 2.2 and forkMode the problem was still there.
I have now patched cobertura itself and the maven plugin, so that it works fine.

The problem was, that for saving the cobertura.ser file, just a shutdown hook was installed. The solution is to trigger cobertura to save the file additionally before the JVM ends. For that I added a new timer task in class ProjectData (see appended class =ConditionalSaveTimer=). Every half second the ConditionalSaveTimer checks if there is a directory "pleaseSaveCobertura" in the directory where the cobertura.ser is saved. If yes, cobertura saves. That is all we do in cobertura.

In the maven plugin we must now create such a "trigger directory" to trigger cobertura to save. We execute the following line in method "executeReport":
"CoberturaDataUtil.waitUntilDefaultCoberturaCoverageFileSecurelySaved(getLog());"
See attached files "CoberturaReportMojo" and "CoberturaDataUtil"

All jars are relased on EL4J's Maven 2 repo. Just use them!
http://public-el4.elca-services.ch/el4j/maven2repository/

<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>cobertura-maven-plugin</artifactId>
<version>2.3-el4j_20100108_1400</version>
</plugin>

Do not forget the configure the plugin twice, in build AND reporting section of your pom!

Because there are two report goals that does execute cobertura, do not forget to configure the reportSets:
<reportSets>
<reportSet>
<id>standardReports</id>
<reports>
<report>cobertura</report>
</reports>
</reportSet>
</reportSets>

To complete the listing, here the cobertura dependency for your dependency management:
<dependency>
<groupId>net.sourceforge.cobertura</groupId>
<artifactId>cobertura</artifactId>
<version>1.9-el4j_20100108_1600</version>
</dependency>

BTW: To record the code coverage while working with the web or gui application, we have created another plugin. See http://el4j.sourceforge.net/plugins/maven-cobertura-runtime-plugin/index.html

Cheers,
Martin Zeltner
http://el4j.sourceforge.net

This issue persists even in version 2.4 release. If anyone has it working such that a calling "mvn clean cobertura:cobertura" produces accurate coverage reports would you please post the relevant POM sections.

I have found that running "mvn clean cobertura:cobertura" yeilds a coverage report of 0%, each subsequent run of just "mvn cobertura:cobtertura" adds the prior test set values to the test reports. So if a section of code is called 3 times the first pass after a clean is shown as 0, the second pass it is shown as 3, the third pass 6, and so on.

2.4 works for me with forkMode=once as I posted above.

HI Friends,

I have the same problem. I have found that though the unit tests have been run successfully, but code coverage is showing as 0%.

Log message is attached below
===========
.
.
Successful Testing.....
tearDown.....
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 22.562 sec

Results :

Tests run: 3, Failures: 0, Errors: 0, Skipped: 0

[INFO] [cobertura:cobertura

]
[INFO] Cobertura 1.9.2 - GNU GPL License (NO WARRANTY) - See COPYRIGHT file
Cobertura: Loaded information on 103 classes.
Report time: 8281ms

[INFO] Cobertura Report generation was successful.
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
.
.
===========================

My plugin configuration is as follows
--------------------------

<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<version>2.5</version>
<configuration>
<includes>
<include>**/Test.java</include>
</includes>
</configuration>
</plugin>

<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>cobertura-maven-plugin</artifactId>
<version>2.3</version>
<configuration>
<includes>
<include>**/Test.java</include>
</includes>
<forkMode>once</forkMode>
</configuration>
</plugin>

-------------------------------

Please help me out. Please let me know if you need any other information.

Thanks
Atanu Panda

The forkMode setting should go into the configuration of the surefire-plugin.