Hello! I have the following scenario:
This behaviour kills our statistics. It seems that we have unreviewed stuff but it is not true for lines. Is it possible to change coverage algorithms or it can be other approach to have right statistics?
By my opinion in this case we should have 100% line coverage( all lines of code in last revision is coveted), 100% patch coverage( the result of pathces is reviewed) and 100% changesets reviewed( we have looked on all changesets).
Every team in the world is unique, and so Atlassian believes that each and every team's best way of working needs to be molded to their unique circumstances – ...
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot