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

How the coverage percentage is getting increased in merge

Team, I have basic and sanity test cases both are running aganist same code line. If I run the basic and sanity in single shot I am getting 27% coverage. But, I am running the basic alone and sanity alone and finally merged both clover.db. Now I am getting 29% coverage. So, Which one is correct.

Eg:        Basic + Sanity = 27 %

             Basic db + merge + Sanity db = 29%.

Please help me .. thanks in advance.


1 answer

1 accepted

0 votes
Answer accepted

Hi Sivaraj,

Did you check all steps listed by me in: 

As I wrote before, the most probably the way you set up Clover in your build is incorrect. And this is a primary reason why you see "weird" coverage numbers. 


In case you can't find the error, feel free to raise a ticket at - please attach entire build log (with debug logging) + build file(s) + clover database(s) generated.



Thanks for your response. Everytime we are cleaning the clover db and cloversrc. But still we are getting same . So the conclusion is "Even though we are merging the clover db we will get identical coverage percentage." Can you please confirm on same.

In case you do run your tests as follows: 1) Create single clover.db and run basic and sanity tests in one run, generate HTML report. and 2) Create clover.db for basic tests, run them; next create clover.db for sanity tests, run them; next merge two clover databases into one; next generate HTML report from a merged database. Then it's quite probable that you have the same source files registered in BOTH Clover databases. For this reason, during a merge, only ONE version of the source file will be picked. Clover does not perform any merge of the same source file from different databases; a reason is simple - in each database you could have a different version of the file, i.e. with different content. As a consequence, it may happen that code coverage for such file in a report generated from a merged database will be lower than in case when single database was created. So your conclusion "Even though we are merging the clover db we will get identical coverage percentage." is not correct.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Marketplace Apps & Integrations

Happy New Year and Welcome New Marketplace Partner Program Partners!

Happy New Year! We hope you all had a safe and restful holiday season. 2020 was a unique year full of unforeseen events; however, as we enter the new year of 2021, we’re optimistic for the light at t...

505 views 7 18
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