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.
Hello, Community! My name is Gosia and I'm a Product Manager on Jira Server and Data Center here at Atlassian. Since 2002 when we launched our public issue tracker, jira.atlass...
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