-
Notifications
You must be signed in to change notification settings - Fork 0
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
Add test-coverage checks to CI #199
Comments
All tests definitely need to pass, but this is about how much code is tested. Test-coverage checkers tell us how much of the total codebase (by lines) is covered by at least one test. We can set a benchmark, like 50%, and not allow merging of branches that increase the amount of untested code to 50%. |
Ah, gotcha 👍 |
Here's an example of a coverage action: https://github.com/marketplace/actions/python-coverage |
Once the repo is open (#265), there are a bunch of free tools we could use, e.g. coveralls.io. |
A good software package has good test coverage! We have basic coverage (#5) but still some large holes (#124, #169). When these are covered, it would be good to maintain that coverage in future, using CI to make sure that new functionality must come with new tests.
The text was updated successfully, but these errors were encountered: