-
Notifications
You must be signed in to change notification settings - Fork 1.2k
"Compilation" error does not report tests in test tree #15204
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
Comments
This might? be related: #15147 |
The PR will partially address this #15129. To actually report this in the test tree, that is a new feature. We 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. |
Hello! Just fixed this in our new python rewrite. Error tolerant discovery is now out on insiders and will go out on stable in the next release. It is part of our testing rewrite and so if you would like to try it yourself, you need to add this setting to your users |
Environment data
python.languageServer
setting: PylanceExpected behaviour
When a test cannot be imported due to code failures (ex: invalid syntax, import errors) I expect the test to be reported in the test view. Its super important to make these errors visible... There are a bunch of tests that contain error and just failed
"silently".
Actual behaviour
The test fails silently and the test is not reported in the test treeview. (it is reported in the
Python Test Log
under output though)Steps to reproduce:
Create a file:
Create a test that imports this function:
Run tests using the test view:
Notice that the class is not identified.
Look at the Python logs:
Logs
Output for
Python
in theOutput
panel (View
→Output
, change the drop-down the upper-right of theOutput
panel toPython
)The text was updated successfully, but these errors were encountered: