Less clover coverage percenatge after merging clover DBs

I have three sub-modules and I'm generating clover coverage report for each one. The code coverage percentage for three sub-modules are 62%, 32% and 0.2%. But, when I merge all three DBs and generate a consolidated report the coverage comes down to 16%. Could someone explain why it comes down that much. If I take average of all coverages, it is around around 30%. Intersetingly, when I check individual class of a sub-module, percenatge matches with consolidated report.

7 answers

This widget could not be displayed.

If I take average of all coverages, it is around around 30%.

How did you calculate the average?

This widget could not be displayed.

We calculated the average by taking the average of 62,32 and 0.2. Apart from this in the merged report the NLOC seems to be higher than the one which we sum with the individual reports. So wanted to know how does it work with the clover merge

This widget could not be displayed.

Hi Ritesh, please note that simple artithmetic average of 62, 32 and 0.2 does not take into account actual size (in terms of number of code elements instrumented) of these three databases.

Please open an HTML report generated from every database separately. On the dashboard these's a box with a text like "<label class="titleText link">Coverage</label> N classes, X / Y elements". Calculate the average as:

coverage [%] = (X1 + X2 + X3) / (Y1 + Y2 + Y3) * 100%

(where Xn / Yn are values from each report)

Is the final result around 30% (i.e. as for a database merged by <clover-merge>)?

This widget could not be displayed.

I applied the suggested formulae with all three reports and the end result of the average is 21% but the mergered report havs coverage of 16%. Also, the result of (X1 + X2 + X3)/(Y1 + Y2 + Y3) is 85751/401396 but when I see X/Y element of consolidated report it's 94,958/585,491. Could you please help.

This widget could not be displayed.

Please create a zip with these three databases and with coverage files as well as with the merged database and raise a ticket at http://support.atlassian.com. I'll be happy to investigate the difference. It would be great if you could also attach build.xml/pom.xml with Clover configuration you have.

This widget could not be displayed.

Hello Marek,Thanks for your response. Due to size constraing I'm not able to upload mentioned files. I have raised a tickcet(CLV-6036) and attached screenshots of report for reference.

This widget could not be displayed.

hello ,

even i'm facing the same issue  after merging clover db - the code coverage percentage has reduce. any updates on this issue.

 

thanks , sahid

Suggest an answer

Log in or Sign up to answer
Atlassian Summit 2018

Meet the community IRL

Atlassian Summit is an excellent opportunity for in-person support, training, and networking.

Learn more
Community showcase
Published yesterday in Marketplace Apps

The 7 hacks of highly successful automation

...there's anything I've learnt from working, it's that people are lazy! No offense to anyone reading this, but it's true and we can all admit it. The easier you make something for someone, the more...

97 views 0 8
Read article

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you