-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Perform partial test discovery with pytest in the face of other test discovery errors #14116
Comments
This would require us to replicate the test discovery of pytest in order to work around pytest erroring out when there's a discovery failure. I have marked this issue as "needs decision" to make sure we have a conversation about your idea. We plan to leave this feature request open for at least a month to see how many 👍 votes the opening comment gets to help us make our decision. |
closing as it is the same as #13301. We have issue 13301 on our schedule for this iteration so hopefully the fix is coming soon! |
For Example, I have 1000 pytest testcases in my project, but only one of them got error (like code defect, or logic issues, and so on...) cause testcase discorvery failed, For now, looks all testcases will not shown in Python Test Explorer List, and CodeLens adornments also not appeared within my testcase code, So It's hard for me to run or debug a normal (not the error testcase), I have to use other debuger tools like ipdb to debug my code. In this case, can we show the normal testcase and just exclude the error(s) in Python Test Explorer List? It's really hard for me if one case failures cause all testcases collect failed.
screenshots:
![image](https://user-images.githubusercontent.com/4414171/94332491-50c8b000-0008-11eb-840c-608f169bd854.png)
Version: 1.49.2 (user setup)
Commit: e5e9e69aed6e1984f7499b7af85b3d05f9a6883a
Date: 2020-09-24T16:29:41.983Z
Electron: 9.2.1
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: 8.3.110.13-electron.0
OS: Windows_NT x64 10.0.19041
Related Links: kondratyev-nv/vscode-python-test-adapter#179
The text was updated successfully, but these errors were encountered: