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
I have a Python repo in which the code coverage extension is showing an error next to the empty __init__.py files claiming that these files have 0% code coverage which is less than the threshold.
I would expect that coverage should show 100% for files with 0 statements. Or at the very least no error should be shown.
Here's the command used to run coverage:
coverage erase && coverage run --concurrency gevent -m pytest && coverage report && coverage html && coverage lcov
And here's the output snippet:
Name Stmts Miss Cover
--------------------------------------------------------
...
xxxx/__init__.py 0 0 100%
...
The above __init__.py file shows up with a red <% symbol next to it in the explorer.
Here is how the extension is configured in my .devcontainer.json file:
I have a Python repo in which the code coverage extension is showing an error next to the empty
__init__.py
files claiming that these files have 0% code coverage which is less than the threshold.I would expect that coverage should show 100% for files with 0 statements. Or at the very least no error should be shown.
Here's the command used to run coverage:
coverage erase && coverage run --concurrency gevent -m pytest && coverage report && coverage html && coverage lcov
And here's the output snippet:
The above
__init__.py
file shows up with a red<%
symbol next to it in the explorer.Here is how the extension is configured in my
.devcontainer.json
file:The text was updated successfully, but these errors were encountered: