clover2:check passes the build while clover2:log shows lower percentage value

Imagine a following scenario:

  • clover2:check has targetPercentage="100%" set
  • build runs with clover2:log and clover2:check goals
  • clover2:check passes, but the clover2:log shows coverage lower than 100%

How could this happen?

1 answer

1 accepted

Accepted Answer
0 votes

A trick is that targetPercentage, statementPercentage, methodPercentage and conditionalPercentage all are being compared against actual project metrics using a numerical precision equal to a number of fractional digits set in these properties. A standard value rounding is used (BigDecimal.ROUND_HALF_EVEN).

For instance, if project's total code coverage is 99.9% and maven-clover2-plugin has a folowing setting:

<targetPercentage>100%</targetPercentage>

then the comparison is made using no fractional digits. Therefore, 99.9 is rounded to 100 and clover2:check passes the build.

Therefore, to reach exactly 100%, maven-clover2-plugin shall have:

<targetPercentage>100.000000%</targetPercentage>

(six digits is enough as project's coverage percentage metric is stored in float)

Suggest an answer

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

Jira Ops Early Access Program Update #1: Announcing our next feature and a new integration

Thanks for signing up for Jira Ops! I’m Matt Ryall, leader for the Jira Ops product team at Atlassian. Since this is a brand new product, we’ll be delivering improvements quickly and sharing updates...

260 views 0 6
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