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)
If you spend enough time as a Jira admin - whether you are managing a single, mid-sized instance, a large enterprise one or juggling multiple instances at once - you will eventually find yourself in ...
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot