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
Right now, the coverage measurement is enabled for pytest-based testing. I fail to find any current usage of this information during the development process. However, I may miss something. By my experiment, this option makes it impossible to use any breakpoint in VSCode during test debugging. See this issue microsoft/vscode-python#693
A workaround to disable the coverage in the developers local VSCode config like so:
Please consider disabling this feature at the project level if it is not used for anything.
The text was updated successfully, but these errors were encountered:
Indeed I have the --no-cov in my settings.json :-)
I use the coverage reports to monitor the situation from time to time. How could we do that in a better way?
I'm open to alternative solutions.
Right now, the coverage measurement is enabled for pytest-based testing. I fail to find any current usage of this information during the development process. However, I may miss something. By my experiment, this option makes it impossible to use any breakpoint in VSCode during test debugging. See this issue microsoft/vscode-python#693
A workaround to disable the coverage in the developers local VSCode config like so:
Please consider disabling this feature at the project level if it is not used for anything.
The text was updated successfully, but these errors were encountered: