Am 12.07.2019 um 08:47 schrieb Lennart Jörelid <[email protected]>: > > There are several comparisons for code coverage project, such as the link > below. > My preferences regarding a coverage tool would be something like: > Alive community Define alive community: there is a user list where questions are answered, there are two very passionate developers who form the core. There is a user-list https://groups.google.com/forum/#!forum/jacoco <https://groups.google.com/forum/#!forum/jacoco> jacoco is the default coverage tool supported by Sonarqube for Java, the default in IntelliJ as well and has excellent Eclipse support as well (this is heresay, but Eclemma is based on jacoco).
> Functioning on JDK 8 and 11 As of version 0.8.4 (May 2019) jacoco even supports JDK12 https://www.jacoco.org/jacoco/trunk/doc/changes.html <https://www.jacoco.org/jacoco/trunk/doc/changes.html> > Maven Plugin integration Support is excellent IMO, you may even differentiate between unit (surefire) and integration (failsafe) tests. There is a merge goal to merge results from several modules. And there is a check goal to fail the build when coverage is too low. https://www.jacoco.org/jacoco/trunk/doc/maven.html > Easy-to-read coverage report https://www.jacoco.org/jacoco/trunk/coverage/ <https://www.jacoco.org/jacoco/trunk/coverage/> this is the report for jacoco itself. One class: https://www.jacoco.org/jacoco/trunk/coverage/org.jacoco.core/org.jacoco.core.internal.analysis.filter/TryWithResourcesJavacFilter.java.html#L231 <https://www.jacoco.org/jacoco/trunk/coverage/org.jacoco.core/org.jacoco.core.internal.analysis.filter/TryWithResourcesJavacFilter.java.html#L231> > I found only the following comparison, but others (and hopefully not done by > one of the coverage tool teams) likely exist. > Do you have others? > http://openclover.org/doc/manual/4.2.0/general--comparison-of-code-coverage-tools.htm > > <http://openclover.org/doc/manual/4.2.0/general--comparison-of-code-coverage-tools.htm>I > have used Atlassian Clover and Cobertura before and now use jacoco already > for a couple of years. Clover had nice reports but instrumented source files and needed another compile, all in all it was dog slow, with WARs you did not test the final binary, handling was a mess. Reporting was nice though. Cobertura was OK but development seemed to have stalled a bit. jacoco works as an java-agent so it supports any JVM language (syntax highlighting in the report might be off a bit, though) and has a TCP server mode, i.e. you may even start your tomcat with it and dump the results after your tests. Overhead when running with jacoco is ~ 10%. Of course you may call me opinionated jacoco still states that I am member of the core team. Unfortunately, as with mojohaus, I have very, very little time due to private obligations. Best Regards Mirko > > Den onsdag 10 juli 2019 kl. 08:32:18 UTC+2 skrev Mirko Friedenhagen: > Hello Lennart, > > +1 for removing cobertura from the mojo-parent, maybe meanwhile use jacoco > instead? > >> Am 10.07.2019 um 05:13 schrieb Lennart Jörelid <[email protected] <>>: >> >> Or we could simply remove the Cobertura plugin from the Mojo-Parent site, >> and include it for those plugins using Cobertura. >> >> While I am uncertain about the state of the Cobertura running on Java8+ (and >> Java 11+ for that matter), it seems that the Mojo integrations with >> Cobertura requires quite a few complex twists within the POM - men to the >> point where it actually hampers progress. Could we remove it from the >> MojoHaus-Parent re-introduce Cobertura when it is actually updated for JDK >> 8+ or JDK 11+? >> >> >> Den tisdag 9 juli 2019 kl. 22:24:51 UTC+2 skrev Jochen Wiedmann: >> On Tue, Jul 9, 2019 at 7:44 PM Lennart Jörelid >> <[email protected] <>> wrote: >> > >> > Actually, it does not. >> > >> > The problem is that the IT:s in mojo-parent version 50 are run with >> > Cobertura instrumentation. >> > The implication of this is that the POM of each IT needs the Cobertura >> > depdendency within the plugin dependencies when running the mvn site goal. >> >> Would declaring the dependency as an extension help? See >> >> https://maven.apache.org/guides/mini/guide-using-extensions.html >> <https://maven.apache.org/guides/mini/guide-using-extensions.html> >> >> Jochen >> >> -- >> You received this message because you are subscribed to the Google Groups >> "mojohaus-dev" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <>. >> To post to this group, send email to [email protected] <>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/mojohaus-dev/591a9b84-cf87-4e0b-9ef1-a75dca9f4850%40googlegroups.com >> >> <https://groups.google.com/d/msgid/mojohaus-dev/591a9b84-cf87-4e0b-9ef1-a75dca9f4850%40googlegroups.com?utm_medium=email&utm_source=footer>. >> For more options, visit https://groups.google.com/d/optout >> <https://groups.google.com/d/optout>. > > > -- > You received this message because you are subscribed to the Google Groups > "mojohaus-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] > <mailto:[email protected]>. > To post to this group, send email to [email protected] > <mailto:[email protected]>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/mojohaus-dev/6cb82c8e-9828-45d3-aac8-4cf4c8339ae9%40googlegroups.com > > <https://groups.google.com/d/msgid/mojohaus-dev/6cb82c8e-9828-45d3-aac8-4cf4c8339ae9%40googlegroups.com?utm_medium=email&utm_source=footer>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- You received this message because you are subscribed to the Google Groups "mojohaus-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/mojohaus-dev/CE130420-42FE-42C5-9EF1-6DDD418FF3D6%40gmx.de. For more options, visit https://groups.google.com/d/optout.
