cobertura

I have a Maven project with 4 modules - 3 of them contain code and some tests (testing equals and hashcode of the classes) whereas the 4th module is for testing the 3 other modules. Now I want to run the cobertura code coverage tool to get an overview which classes are well tested and which are not. I did some investigations on that topic and it seems that cobertura is not aware of generating the right code coverage percentages and line coverages, if some sources which are tested are located within other modules. I have read over some links like SeamTestCoverageWithCobertura and Using the

Any ideas when cobertura will support java 7? Found http://sourceforge.net/tracker/index.php?func=detail&aid=3295711&group_id=130558&atid=720018 We preferred cobertura over emma and other code coverage tools and looks like we have to redo all those again, now that none of them support java 7 yet. Thanks Cobertura 2.0.3 supports Java 7, the cobertura-maven-plugin version 2.6 which uses this version has been just released T.K. I was able to get it to work by adding the following argument: -XX:-UseSplitVerifier I got it from here . I think the answer is: it won't. There is discussion on the

This sonar page basically lists the various methods employed by different code coverage analysis tools: Source code instrumentation (Used by Clover ) Offline byte code instrumentation (Used by Cobertura ) On-the-fly byte code instrumentation (Used by Jacoco ) What are these three methods and which one is the most efficient and why?If the answer to the question of efficiency is "it depends" , then please explain why? Source code instrumentation consists in adding instructions to the source code before compiling it. These instructions are used to trace which parts of the codes have been executed

In our project, we run both junits and cobertura using maven. The problem I am facing is that, junit test cases are running twice, once before the jar creation process and then once again for generating cobertura coverage reports. When running cobertura and junits with ant, we run junits only once since, cobertura runs along with junits. Is there a way to configure the above case with maven. I know we can use "maven.test.skip" property to skip junits. But when I do this, I am not able to see junit xml & html file reports. Also, in maven how to configure junits to run in batch or parallel ?

Is there a way to exclude code from inclusion into Cobertura coverage reports? We have some methods that should not be included in the coverage report and therefore not drive down the coverage numbers. I know that Clover has such a functionality, but I have not found anything similar for Cobertura. Juha Syrjälä You can exclude classes from instrumentation. Then they should not appear on reports. See exclude statements below. You can also ignore calls to some methods. See ignore statement below. If you are using maven, see maven plugin manual . <configuration> <instrumentation> <ignores>

I have switched to the newest JDK 7 and I am having problems with running testng unit test on byte code that is fiddled by emma coverage tool. None of my test cases are run correctly and for most of them I am receiving such errors. java.lang.ClassFormatError: Illegal local variable table length 10 in method measurement.meter.AbstractSerialPortMeter.<init>(Lmeasurement/meter/SerialPort;)V at measurement.meter.Elc3133aTest.setUp(Elc3133aTest.java:42) I have found an article here JSR 292 Goodness Fast Code Coverage Tool Less 10k , which is saying that "JSR 292 introduces a new bytecode