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

[Marek Parfianowicz]

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?

[Marek Parfianowicz · Accepted solution]

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)