Want to show your appreciation? Please to my charity.

Saturday, January 21, 2012

Cobertura and Eclipse (eCobertura)


Cobertura is a free Java tool that calculates the percentage of code accessed by tests. It can be used to identify which parts of your Java program are lacking test coverage. It is widely used in the continuous integration process to ensure the unit test was written to exercise the application code. Developer should also run the code coverage on the development environment to make sure there is enough code coverage before commit the changes into center source repository.

Eclipse Integration

The most convenient way to use Cobertura is to run it right in the Eclipse IDE using eCobertura (Eclipse Plugin for Cobertura). eCobertura enables you to launch your applications or tests in Cobertura-covered mode directly from within Eclipse. View your source files colored according to the coverage results. Browse through the detailed coverage results in a tree view.

Install eCobertura

Use Eclipse menu item “Help->Install New Softwre…” to install the plugin from the location indicated below.

Note For detailed instruction of how to install Eclipse plugins, please refer to General Installation Instructions section of Install Eclipse and Commonly Used Plugin page.

Work with URL: http://ecobertura.johoop.de/update/
Features to be selected to install:

  • eCobertura Code Coverage
    • eCobertura

NOTE: If you are trying to install on Kepler, please see the workaround in the end of this post

Run Coverage

You can run your applications or tests in Cobertura-covered mode in different ways. We’ll discuss a few of them but our main focus is to show you how to run the JUnit test with eCobertura. Running as application or with a different test framework is similar but will not be discussed here.
You start by selecting an application, a package, a test class, or a test method in the package explorer, the source editor, or anywhere that JUnit test can run. Then use toolbar button, context menu, or “Run” menu item to run the coverage.

Example 1, use toolbar button’s pull down menu to run all JUnit tests of a project in Cobertura-covered mode. Using toolbar button is the most convenient way launch Cobertura. It maintains a list of recently executed coverage run so that you can access them quickly. You’ll find it is very handy to repeat your last coverage run by directly clicking on the button itself.

Example 2, use context menu to run all JUnit tests of a selected package in Cobertura-covered mode.

Example 3, use “Run” menu to run all JUnit tests of a test class in Cobertura-covered mode. Using “Run” menu item maybe convenient for keyboard intensive users. The key sequence is Alt, R, C, then select a number (typically 1 or 2 depends on what you have selected).

Check Coverage

After the coverage run, the detailed coverage result is presented in “Coverage Session View” window and coloring in the source editor.
Coverage Session View
The coverage session view let you browse through the detailed coverage results in a tree view. It displays the code coverage at both line and branch level for each class. Results of each class are summarized in subtitle for each package and grant total for all packages. You can double click on the classes in the tree view to jump to their respective source editors.
There are a few known issues with “Coverage Session View” windows, please follow the links to see a solution or workaround.
  1. The view is hidden by default. You need to show coverage session view upon first coverage run.
  2. The view isn’t automatically brought to front after every coverage run. Use shortcut key binding can ease the inconvenience.
  3. Coverage session view stops updating itself sometimes. Restart Eclipse when it happens.
Source code coloring
eCobertura also colors the source files according to the coverage result. Lines with green background are covered and those with pink background are not. For example,
Note: eCobertura still cannot visualize branch coverage at this moment so you may need to run the Cobertura along and generate the html report if you must know the missing branch coverage.


eCobertura often instruments much more classes than you intended to. Classes do not belong to current project, test classes and mocks add a lot of noise to the coverage result. eCobertura still has no smart way of detecting which class should be include/excluded. Hence, you’ll have to configure your coverage run to get a sensible aggregated percentage. Fortunately, you only need to do it once for reach project.
  1. Use toolbar button pull down or context menu to open “Coverage Configurations” dialog. 
  2. Select the project in the left run tree. If you don’t see your project, you can add it manually or simple go back and run the coverage once for the project and come back here.
  3. Click on the Filters tab on the right and defined include/exclude filters according to your project. While exclude filters are usually always the same, you'll need one or more filters to include all the packages in your project.
  4. Click on Apply button and then close the dialog.

Known Issues

Show Coverage Session View
The “Coverage Session View” is hidden by default and you have to show it manually.
Show View For detailed instructions on how to show feature window, please refer to Access Feature Window section of Eclipse and Common Plugin Installation.
Shortcut key binding to show Coverage Session View
Version 0.9.8 of eCobertura doesn’t automatically bring the “Coverage Session View” window to front after coverage run. You’ll have to click on the Coverage Session View tab every time. Experienced user can ease the inconvenience by defining a shortcut key binding for show view command in preferences.
Coverage Session View stops updating

It is a known bug in version 0.9.8 of eCobertura that the “Coverage Session View” may sometimes stop updating itself after coverage run. You'll notice the issue when the execution time following the “All Packages” doesn’t update any more; and the tree remains opened from run to run. When this happens, the only known fix is to restart Eclipse.

Update (9/2/2012): I have now switched to EclEmma (not complete see 2nd update below). Don’t be fooled by the name. Emma is just the history, it no longer uses Emma. Instead, it uses JaCoCo coverage engine that can provide save level of granularity of coverage information but integrates with Eclipse much better than eCobertura. The only thing I have missed is the ability to see both line and branch coverage in the eCobertura’s coverage session view. EclEmma only allows you to see one at a time.

Update (4/16/2013): I'm actually using both, because of the EclEmma problems people mentioned below. Although I use EclEmma in most of time, but I still need eCobetura for edge cases and always run Cobertura on build server.

Install on Kepler

If you are using the Kepler version of eclipse, than the eCobertura won’t install because it is looking for an old version of JUnit.

Update (11/22/2013): There are two workarounds to this problem. You only need to do one of those.

  1. Instead of installing a new copy of Kepler. Try to upgrade from an old version of eclipse. I had Juno running with eCobertura installed. After upgrading to Kepler, the eCobertura still works faultlessly. The upgrade process was painless if you follow the instructions here. Actually it is such a good experience that I don’t have to re-install all the plugins that I had since Indigo.
  2. You need to copy a old JUnit plugin, get it from your old installation of eclipse like Indigo or Juno. Not sure which exactly version worked but I copied both org.junit4_4.8.1.v20120523-1257 and org.junit_4.10.0.v4_10_0_v20120426-0900 to the plugins directory and then you can install eCobertura.


Anonymous said...

EclEmma doesnt work with PowerMock. eCobertura does work with PowerMock.

Anonymous said...

@anonymous, you are right and I noticed the same. But I made minimal to no use of powermock, so it is not an issue for me. Let see if eCobertura will fix those minor but annoying problems first or eclemma will fix the powermock issue first.

Anonymous said...

Any idea how to generate report with ecobertura plugin of eclipse, within eclipse ??
In eclemma I just right click on project and export the report .

Kenneth Xu said...

Well, when I was using ecobertura, I recall that I was able to find the HTML report somewhere that I don't remember. Try to look around. As a last resort, you can always run maven to create the report.

Anonymous said...

Just to note, I found that EclEmma will completely miss anything covered by reflection, but eCobertura seems to recognize it.

Kenneth Xu said...

@Anonymous, true and that's why I'm now using both. Most of time I use EclEmma and eCobertura to cover edge cases and final test before commit.

Anonymous said...

i have to generate html for cobertura report .so, where to create html? can u help me?

Shobana C said...
This comment has been removed by the author.
Shobana C said...

i could not get updates for cobertura.ser file while startup the server... anybody can tell the solution for?

Anonymous said...

I am not able to install it on Eclipse Kepler, get the following

Cannot complete the install because one or more required items could not be found.
Software being installed: eCobertura (ecobertura.feature.group
Missing requirement: eCobertura (ecobertura.feature.group requires 'org.junit4 0.0.0' but it could not be found

Anonymous said...

Anyone have a solution for this great plugin in comination with eclipse kepler?

Kenneth Xu said...

There are different ways to generate HTML for cobertura. I use maven. "mvn cobertura:cobertura" and find HTML in target/site/cobertura

Kenneth Xu said...

Updated the solution to install on Eclipse Kepler.

Anonymous said...

"I am not able to install it on Eclipse Kepler, get the following

Cannot complete the install because one or more required items could not be found.
Software being installed: eCobertura (ecobertura.feature.group
Missing requirement: eCobertura (ecobertura.feature.group requires 'org.junit4 0.0.0' but it could not be found"

I copied from Eclipse Juno into Kepler:

org.junit4_4.8.1.v20120523-1257 org.junit_3.8.2.v3_8_2_v20100427-1100

Now ecobeurta can be installed from update site

rave763 said...

Thanx a lot for the solution to install in kepler, I just downloaded org.junit4_4.8.1.v20120523-1257 online and placed in plugins folder it worked :)

Unknown said...

Thanks for the information about include/exclude filters. Needed when test class coverage needed to be excluded.

Post a Comment