search

alexmojaki / executing

Get information about what a Python frame is currently doing, particularly the AST node being executed
MIT License
326 stars 32 forks source link

Include new library files in coverage measurement #52

Open alexmojaki opened 1 year ago

alexmojaki commented 1 year ago

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.

15r10nk commented 1 year ago

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.

pwwang commented 1 year ago

You need a .coveragerc file, specially with omit section:

https://coverage.readthedocs.io/en/latest/config.html#run-omit

alexmojaki commented 1 year ago

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.