Run time code coverage using Emma

Emma is a free java code coverage tool which measures and reports code coverage of java based products. The most important and usable factor of Emma is, its ability to measure code coverage during the application runtime. At WSO2, we have been searching for a tool to get QA test coverage of our middleware products. Automated QA tests are executed against the binary products. Therefore, source level unit test coverage does not help to identify the figures of QA test coverage. Emma was the best tool which satisfied our requirements.

The procedure is quite simple. Suppose you are going to get the coverage of a binary which obviously contains hundred of jars. First, you need to prepare a list of jars which requires to be instrumented. The list can be prepared easily in *nix environments as follows.

xargs -n 1 $JAVA_HOME/jre/bin/java -cp emma.jar emma instr -m overwrite -cp < jarlist.txt

This inserts tracking code to the jars listed in jarlist.txt.

Now, you should restart your application and Emma starts to gather coverage data. If you have an automated functional test suite, run it over the instrumented binary or test the product manually.

After completing the testing, stop your application. Now, we need to generate the coverage report. Issue the following command.

java -cp emma.jar emma report -r html -in coverage.em,coverage.ec

This generates an html report as shown below.





Currently, we are in the process of developing a selenium based automation framework and we use this test coverage mechanism to find out the components which require more tests.

Comments

Unknown said…
How would i go about this solution in a Windows environment? Can I utilize this with a single .WAR?
June 1, 2009 at 5:58 AM
Heath Gerhardt said…
The solution is almost identical in windows. It's all Java after all. The only difference I can see is the command he used to execute the instrumentation.
August 30, 2009 at 7:50 PM
indrasenareddy said…
coverage.ec is not generating. I am trying my application in tomcat.

I have done the following steps:
1. I have deployed my application in tomcat
2.i have copied emma.jar to C:\Program Files\Java\jre1.5.0_21\bin\lib\ext

3. My tomcat5w.exe, contain the following info:
JVM as: C:\Program Files\Java\jre1.5.0_21\bin\client\jvm.dll
Java Options:
-Demma.coverage.out.file=D:\Tomcat 5.5\emma\coverage.ec
-Demma.coverage.out.merge=true

4. Now i have instrumented the deployed application as below.
java -cp emmar.jar emmae instr -m overwrite -cp "D:\Tomcat 5.5\webapps\ROOT\WEB-INF\classes\com"
and coverage.em has generated in C:\Program Files\Java\jre1.5.0_21

5.Now i have started my tomcat and did some transaction.
when i see in stdout.logs ,i am getting
EMMA: collecting runtime coverage data ...

EMMA: runtime controller started on port [47653]

6.Stopped the tomcat
7.i tried to find coverage.ec in D:\Tomcat 5.5\bin
and also in C:\Program Files\Java\jre1.5.0_21\

but i could not found this file.

8.And also tried the application to run from command line prompt,there also i couldnot found the file.

9.i also set my jre path java_home in environment variables
June 15, 2011 at 6:42 AM
Post a Comment

Popular posts from this blog

WSO2 Stratos - Introducing WSO2 middleware Platform as a Service (PaaS)

Image
Yesterday we released our newest integrated cloud middleware platform, WSO2 Stratos . It is now online and ready for use! For the past few years, WSO2 has been doing many releases based on revolutionary Carbon platform , which helped to consistently improve the platform with introducing latest state-of-art technologies. The initial releases of Carbon product platform intended to improve the features of the individual products. For example, a lot of core features were introduced to WSO2 ESB, WSAS, Governance Registry etc.. Then we focused on ease of integration and more component based model. We introduced Equinox based provisioning model to build your SOA platform by picking and choosing the components as and when you need. Then, the core product platform has been enhanced to support multi-tenancy. With the multi-tenant supported architecture at hand, our brilliant development team was able to introduce the first ever comprehensive middleware PaaS. Why is this so important? Now, WSO2 C...
Read more

Common mistakes to avoid in WSO2 ESB - 1 - "org.apache.axis2.AxisFault: The system cannot infer the transport information from the URL"

In the next few weeks, you could expect a series of blog posts from me which explain the remedies to avoid some common mistakes which we do when working with WSO2 ESB . This is the first of many. During the initial rounds of testing your integration solution or even in production systems, you may have come across the following error. org.apache.axis2.AxisFault: The system cannot infer the transport information from the URL .... Some of you may have struggled hours figuring out a solution to address this issue. Let me explain this error in detail and possible causes of this. So, next time when you see this error in your WSO2 ESB setup, you will not have to spend time unnecessarily googling everywhere. There can be many different causes of this error. I have observed  four main reasons. Cause 1 This is the simplest cause. Suppose, you have a proxy service similar to the following. <proxy xmlns="http://ws.apache.org/ns/synapse" name="MistakesTest...
Read more

Working with HTTP multipart requests in soapUI

Image
You can use HTTP request test step in soapUI to submit messages with various Content-Types.  In this post, we will have a quick look into the multipart/form-data requests in soapUI. multipart/form-data requests usually come into action when you do HTML form submissions with file attachments. For example, have a look at the following HTML form post. <form action="http://localhost:8090/CKFileUploadApp/UploadServlet" method="post" enctype="multipart/form-data"> <input type="file" name="file"> <input type="text" name="paramName"> <input type="submit" name="Submit" value="Upload File"> </form> In the forms like above, we have file upload option as a form input where we can upload a file along with the form submission. In that case, the request's HTTP content type will be multipart/form-data. How can we simulate such a request using soapUI...
Read more