cobertura

I have been trying unsuccessfully for the last few days to run Cobertura 2.4 with Maven 3.0.2. We have a very large project with many modules (sub-projects). What I found is that documentation is basically non-existent or plain wrong. All tutorials I was able to find don't work with Maven 3.x (they build, but Cobertura either doesn't run or cannot generate the reports). Has anyone here been able to make it work? Any useful tips/examples? Thanks. I successfully integrated Cobertura in my projects with adding this: <build> <plugins> <plugin> <groupId>org.codehaus.mojo</groupId> <artifactId

In my project I need to create Cobertura Code Coverage report from Hudson using maven build. In Hudson I have added the Cobertura Code Coverage plugin. I need the complete modification steps of pom.xml. Did you try to add this to your pom.xml in the reporting section? <plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>cobertura-maven-plugin</artifactId> <configuration> <formats> <format>html</format> <format>xml</format> </formats> </configuration> </plugin> Complete configuration steps can be found here . Hudson needs a you to generate the coverage.xml file. To do this without changing

I use the Cobertura Maven plugin for one of my project. But I have a question about the generated report: What is the difference between line and branch coverage? Kane Line coverage measures how many statements you took (a statement is usually a line of code, not including comments, conditionals, etc). Branch coverages checks if you took the true and false branch for each conditional (if, while, for). You'll have twice as many branches as conditionals. Why do you care? Consider the example: public int getNameLength(boolean isCoolUser) { User user = null; if (isCoolUser) { user = new John(); }

What I am trying to achieve is integrate SonarQube analysis into the build process, so that whenever mvn clean install is run, the code is analyzed with SonarQube. We want to use it for local analysis and also for build on Jenkins. If new issues are found, than the build should fail (we want to use build breaker plugin for that). This way the developer would know that by his code his is going to introduce new issues, and will have to fix them for the build to work. When I run mvn sonar:sonar , the analysis takes 30 seconds, which is OK. However, the problem occurs when I am trying to bind

I'm trying to apply code coverage using Cobertura. The app is deployed in Tomcat 5, but when I instrument the .class files, the app stops working. This are my steps: Compile the app (This run in tomcat) Instrument the class files. D:\test\cobertura-1.9.4.1\cobertura-instrument.bat --destination D:\test\instrument D:\src\path_to_app\main\target\webapp Overwrite the class files of D:\src\path_to_app\main\target\webapp with the instrumented class files in D:\test\instrument . Deploy the app in Tomcat via Catalina conf or by a war file. (The app does not work) Does someone have the correct steps