-
Couldn't load subscription status.
- Fork 567
Minimum coverage by group check #1105
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Minimum coverage by group check #1105
Conversation
37f41fc to
539a61f
Compare
ace4fb8 to
4846449
Compare
4846449 to
f17969d
Compare
f17969d to
c7835b5
Compare
|
Lovely! This is also helpful when enabling the new coverage for eval. So we can enable coverage for erb files without dropping the global coverage. |
|
This would be a very welcome change indeed! |
|
Any updates regarding this pull request? |
|
@PragTob This additional functionality for setting minimum coverage by group would be very valuable. We're currently restructuring our Rails monolith to group functionality via Packwerk packages, allowing us to track overall coverage as well as per-package coverage separately via groups. Being able to systematically ratchet down coverage requirement on a per-package basis would be amazing. Would you mind looking into this PR? |
|
WANT |
|
That'd be an awesome feature. |
I added support for coverage checking by group since we needed it for our project and noticed there was an open issue about it. This feature is useful as we’re gradually increasing test coverage across our app, so we can enforce coverage checks on specific parts. Here’s an example of how to use it from the README.