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)
Hi, Atlassian Community! My name is Brittany Joiner and I am a Trello enthusiast and Atlassian Community Leader. I'll be sharing with you a series of videos with my top tips on how to best use Tre...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events