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

0 votes
Accepted answer

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
Asked Thursday in Jira Ops

I'm John Allspaw, Ask Me Anything about incident analysis and postmortems

I'm John Allspaw, co-founder of   Adaptive Capacity Labs, where we help teams use their incidents to learn and improve. We bring research-driven methods and approaches to drive effective inciden...

5,421 views 21 17
View question

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