Skip to content
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

Clean up coverage instructions #107

Closed
brettcannon opened this issue Feb 11, 2017 · 1 comment
Closed

Clean up coverage instructions #107

brettcannon opened this issue Feb 11, 2017 · 1 comment

Comments

@brettcannon
Copy link
Member

Thanks to Codecov and Travis, not only do we have continuous code coverage reports, but we have included instructions on how to run coverage.py as well. Once python/core-workflow#18 is dealt with we should strip those instructions down to their bare minimum and rely more on Codecov for where people can get current coverage results and Travis for instructions on how to run things.

@brettcannon
Copy link
Member Author

Another thing we may want to do is emphasize people should focus on low-hanging fruit when it comes to coverage instead of trying to get every hard-to-reach corner of a module. They should also not initially worry about code not covered by the requisite test module -- e.g. importlib only being tested by test_importlib -- and instead worry about testing as a whole from the entire CPython test suite.

@willingc willingc closed this as not planned Won't fix, can't repro, duplicate, stale Oct 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants