-
Notifications
You must be signed in to change notification settings - Fork 32
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
Include new library files in coverage measurement #52
Comments
Can we also add the tests/ folder to the coverage analysis? It should be assumed that the tests are always executed to 100% but I experienced several times that this is not always the case. The error reporting for example had some issues in #51, which was not noticeable because it was not covered by the tests. Some way to generate the coverage html reports locally would also be helpful. |
You need a https://coverage.readthedocs.io/en/latest/config.html#run-omit |
If you want, but let's consider that a higher goal. It's not something I've done before.
For the main library files, probably not. If we include the tests folder, that'd probably be a good way to exclude samples. |
Currently GHA has
coverage run --include=executing/executing.py <run tests>
which doesn't measure coverage in the recently added files in theexecuting
folder. The original motivation was lines in__init__.py
that would never be covered, but that should be handled by a# pragma: no cover
comment or something.The text was updated successfully, but these errors were encountered: