You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently GHA has coverage run --include=executing/executing.py <run tests> which doesn't measure coverage in the recently added files in the executing 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:
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.
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.
If you want, but let's consider that a higher goal. It's not something I've done before.
You need a .coveragerc file, specially with omit section:
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: