Imagine a following scenario:
How could this happen?
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:
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:
(six digits is enough as project's coverage percentage metric is stored in float)
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Heya, Hipchat friends! We’re so happy you’re checking out Stride. Whether you know it or not, you have been instrumental in making Stride come to life. Every feature, design, and functionality...
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!
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