are you referring to some target coverage percentage per package? If so there's unfortunately no such option. Clover can enforce target coverage but only for whole project.
You could workaround this behavior with multiple builds and instrumenting only package you want to test right now and enforce target coverage, but this is probably not the best way to go on this.
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