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

This widget could not be displayed.

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 support.atlassian.com - please attach entire build log (with debug logging) + build file(s) + clover database(s) generated.

 

Cheers
Marek 

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
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 56m ago in Bitbucket

Branch Management with Bitbucket

As a project manager, I have discovered that different developers want to bring their previous branching method with them when they join the team. Some developers are used to performing individual wo...

15 views 0 3
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