Skip to main content

Java code coverage using cobertura

Code coverage is important as it gives developers confidence in the code that they are checking in. And for a startup automated test and measuring code coverage is equally important to be able to Ship early and be nimble.  I recently automated unit testing in jenkins and wanted to measure how much code coverage we have. So I integrated cobertura in the build framework. Cobertura is a build time instrumentation plugin so the steps are:

1) compile the code
2) Instrument the classes to generate instrumented classes with cobertura hooks.
3) modify junit class path to put instrumented classes before real classes
4) add a system property in junit ant task, so that cobertura knows where to write its statistics.
5) generate a coverage report in html to be used by developers
6) generate a coverage report in xml so that it can be published to sonar so we can do trends on code coverage release after release.

Here is how a typical code coverage report looks like http://cobertura.sourceforge.net/sample/



Here are some more details on the steps:

    <target name="instrument" description="Run Tests">
        <delete file="${basedir}/cobertura.ser" />
        <delete dir="${basedir}/build/instrumented-classes" />
        <cobertura-instrument todir="${basedir}/build/instrumented-classes">
            <ignore regex="org.apache.log4j.*" />
            <fileset dir="${basedir}/build/classes">
                <include name="**/*.class" />
                <exclude name="**/*Test.class" />
            </fileset>
        </cobertura-instrument>
    </target>


        <junit tempdir="${basedir}/build" printsummary="on"
               fork="yes"
               forkmode="perBatch"
               haltonfailure="true"
               failureproperty="tests.failed"
               showoutput="false">
            <jvmarg value="-Djava.awt.headless=true"/>
              <jvmarg value="-Djava.io.tmpdir=${basedir}/build/jenkinstest"/>
            <jvmarg value="-Dnet.sourceforge.cobertura.datafile=${basedir}/cobertura.ser" />           
            <classpath location="build/instrumented-classes" />
            <classpath refid="${testClasspathRefId}"/>
            <classpath refid="cobertura.classpath" />
            <formatter type="plain" usefile="false"/>
            <batchtest todir="${basedir}/${testReportsDir}">
                <fileset dir="${basedir}/${build}/classes">
                    <include name="**/*${testClassPattern}.*"/>
                    <exclude name="**/*$*.*"/>
                </fileset>
                <formatter type="xml"/>           
            </batchtest>
        </junit>


    <target name="coverage">
        <delete file="build/cobertura.ser" quiet="true" />
        <delete dir="build/coverage"  quiet="true"/>

        <cobertura-merge datafile= "build/cobertura.ser">
            <fileset dir="${basedir}/">
              <include name="**/cobertura.ser"/>
            </fileset>
        </cobertura-merge>   
        <cobertura-report format="html" destdir="build/coverage" datafile= "build/cobertura.ser">
            <fileset dir="${basedir}" includes="**/*.java"/>
        </cobertura-report>   
        <cobertura-report format="xml" destdir="build/coverage" datafile= "build/cobertura.ser">
            <fileset dir="${basedir}" includes="**/*.java"/>
        </cobertura-report>
        <cobertura-check haltonfailure="false" />
    </target>


Comments

Popular posts from this blog

RabbitMQ java clients for beginners

Here is a sample of a consumer and producer example for RabbitMQ. The steps are
Download ErlangDownload Rabbit MQ ServerDownload Rabbit MQ Java client jarsCompile and run the below two class and you are done.
This sample create a Durable Exchange, Queue and a Message. You will have to start the consumer first before you start the for the first time.

For more information on AMQP, Exchanges, Queues, read this excellent tutorial
http://blogs.digitar.com/jjww/2009/01/rabbits-and-warrens/

+++++++++++++++++RabbitMQProducer.java+++++++++++++++++++++++++++
import com.rabbitmq.client.Connection; import com.rabbitmq.client.Channel; import com.rabbitmq.client.*; public class RabbitMQProducer { public static void main(String []args) throws Exception { ConnectionFactory factory = new ConnectionFactory(); factory.setUsername("guest"); factory.setPassword("guest"); factory.setVirtualHost("/"); factory.setHost("127.0.0.1"); factory.setPort(5672); Conne…

Logging to Graphite monitoring tool from java

We use Graphite as a tool for monitoring some stats and watch trends. A requirement is to monitor impact of new releases as build is deployed to app nodes to see if things like
1) Has the memcache usage increased.
2) Has the no of Java exceptions went up.
3) Is the app using more tomcat threads.
Here is a screenshot

We changed the installer to log a deploy event when a new build is deployed. I wrote a simple spring bean to log graphite events using java. Logging to graphite is easy, all you need to do is open a socket and send lines of events.
import org.slf4j.Logger;import org.slf4j.LoggerFactory; import java.io.OutputStreamWriter; import java.io.Writer; import java.net.Socket; import java.util.HashMap; import java.util.Map; public class GraphiteLogger { private static final Logger logger = LoggerFactory.getLogger(GraphiteLogger.class); private String graphiteHost; private int graphitePort; public String getGraphiteHost() { return graphiteHost; } public void setGraphite…

What a rocky start to labor day weekend

Woke up by earthquake at 7:00 AM in morning and then couldn't get to sleep. I took a bath, made my tea and started checking emails and saw that after last night deployment three storage node out of 100s of nodes were running into Full GC. What was special about the 3 nodes was that each one was in a different Data centre but it was named same app02.  This got me curious I asked the node to be taken out of rotation and take a heap dump.  Yesterday night a new release has happened and I had upgraded spymemcached library version as new relic now natively supports instrumentation on it so it was a suspect. And the hunch was a bullseye, the heap dump clearly showed it taking 1.3G and full GCs were taking 6 sec but not claiming anything.



I have a quartz job in each jvm that takes a thread dump every 5 minutes and saves last 300 of them, checking few of them quickly showed a common thread among all 3 data centres. It seems there was a long running job that was trying to replicate pending…