Skip to content
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

Unit test discovery error output too verbose #17105

Closed
gregvanl opened this issue Aug 24, 2021 · 1 comment
Closed

Unit test discovery error output too verbose #17105

gregvanl opened this issue Aug 24, 2021 · 1 comment
Labels
area-testing bug Issue identified by VS Code Team member as probable bug partner ask

Comments

@gregvanl
Copy link

Testing #17039

When there is an issue with test discovery, the Test Explorer tree displays a recommendation to look at the output panel (see Output > Python).

This output is too long and includes several scroll pages of Python source code. There error output should be scoped to just the test discovery error.

@github-actions github-actions bot added the triage-needed Needs assignment to the proper sub-team label Aug 24, 2021
@karthiknadig karthiknadig added area-testing bug Issue identified by VS Code Team member as probable bug partner ask triage and removed triage-needed Needs assignment to the proper sub-team triage labels Aug 24, 2021
@karthiknadig karthiknadig removed their assignment Aug 30, 2021
@github-actions github-actions bot removed the needs PR label Aug 9, 2022
@karrtikr karrtikr added the needs PR Ready to be worked on label Aug 9, 2022
@eleanorjboyd
Copy link
Member

Hello! I have reviewed this issue and given the architectural changes of the testing rewrite, this issue should no longer exist on the rewrite. Therefore I am going to close this issue but please comment or open a new issue if you are still seeing a problem when you try this yourself!

To use the rewrite yourself just add ”python.experiments.optInto": ["pythonTestAdapter"] to your user settings. You can confirm you have the rewrite enabled by setting your log level to trace, via the Developer: Set Log Level command in the command palette. Then check to see if Experiment 'pythonTestAdapter' is active is in your python logs.

Thanks!

@github-actions github-actions bot removed the needs PR Ready to be worked on label Oct 30, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 30, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-testing bug Issue identified by VS Code Team member as probable bug partner ask
Projects
None yet
Development

No branches or pull requests

4 participants