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

Error output discards actual error message (feature request) #377

Open
LordSyd opened this issue Feb 20, 2023 · 0 comments
Open

Error output discards actual error message (feature request) #377

LordSyd opened this issue Feb 20, 2023 · 0 comments

Comments

@LordSyd
Copy link

LordSyd commented Feb 20, 2023

Hi,

I had a problem with the extension not finding any tests. As it turned out in actuality my windows env-variables were broken. But I would have never been able to debug that, because the extension discards the native error thrown during test discovery and instead prints a generic, not very helpful error message.

Could you please change this to include the actual error thrown into the message? This cost me a few hours to debug, because I searched in the completely wrong direction - with the error message it would have taken me half an hour...

In my case, all I did was change the error output in the testDiscovery.js file at line 46 to this:

logger_1.Logger.LogError(`Error while executing ${command}: ${err}`, stdout);

This gave me the information needed to debug my error.

Regards,
Daniel

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant