Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Unable to understand branch coverage and line coverage for Android in Dashboard


We have integrated Clover for Android in Eclipse IDE. We are able to generate the html report of the project. But when we open the dashboard of that html page we are not able to see the line coverage and branch coverage of the overall project. It is giving the coverage as per the package or class . We need for the overall project.

Can you please help us how to read the dashboard and understand various aspects of it.

Help Appreciated.



3 answers

1 accepted

0 votes
Answer accepted

Hi Bhushan,

The dashboard itself is not configurable, however you can configure content of detailed reports for packages and classes. In order to do this, you'd have to use Ant and generate HTML report outside Eclipse. The task can contain one or more elements and you can choose which metrics shall be displayed in the report. Please see for more details. If you'd like to learn more about metrics and reports, I suggest a following lecture:





We need the line coverage and branch coverage of the overall project.

0 votes

We need the line coverage and branch coverage of the overall project.

Strictly speaking, Clover does not have a line coverage metric. Instead of this, a statement coverage metric is available (which is quite similar in terms of granularity).

Another question is how do you interpret branch coverage - is it a coverage of branches only (i.e. decision blocks like "if") or is it a coverage of statements + branches. In my opinion it should be the latter one, but it's up to you.

In order to read coverage value for the whole project, you can generate XML report. In the beginning of the file you'll find a <project> tag, for instance:

&lt;coverage generated="1370605007732" clover="3.1.12"&gt;
   &lt;project timestamp="1370605007039"&gt;
      &lt;metrics conditionals="46" methods="31" classes="3" files="3" packages="1" coveredstatements="90" complexity="54" loc="285" ncloc="183" coveredmethods="31" coveredconditionals="39" statements="95" coveredelements="160" elements="172"/&gt;

You can calculate coverage as follows:

  • method coverage = coveredmethods / methods * 100%
  • statement coverage = coveredstatements / statements * 100%
  • branch coverage = (coveredconditionals + coveredstatements) / (conditionals + statements) * 100%
  • total coverage = coveredelements / elements

Note: a total coverage metric is described here.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira

Jira Cloud Performance Improvements

Hello everyone, I am a product manager in the Jira Cloud team focused on making sure our customers have a delightful experience using our products. Towards that goal, one of the areas which is extr...

146 views 1 8
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you