-
Notifications
You must be signed in to change notification settings - Fork 5
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
IdeaJasmine does not see node.js interpreter ran in WSL2 #21
Comments
I haven't worked with WSL2, but based on a quick web search it looks like there are a number of steps you have to go through to get it working with IntellJ, and a few pitfalls. I wonder if your problem is specific to the IdeaJasmine plugin or if IntelliJ just isn't working right with WSL2 at all. Are you able to get a Node.js run configuration working in your project, or does it give you the same error? What happens if you try to run your tests using a Mocha or Jest configuration? (You'd most likely have to temporarily install Mocha or Jest to do this.) Do you get the same error, or does Mocha/Jest start up and complain about problems with your specs? |
Frankly I haven't tested any other testing frameworks with that project, for now all I can say that's I can successfully run ts node.js application via intellij (with project and node.js v16.16.0 installed with nvm located on WSL). |
No need. If you're able to run a Node configuration, I think that's enough to show that your basic setup is working. I'll see if I can reproduce this when I get a chance. |
I've been unable to get Node working inside WSL2 on the only Windows machine I have access to, so I won't be able to investigate this. But if you (or anyone else) want to put together a PR that fixes the problem, I'd be happy to review it. |
Having below configuration:
When I'm trying to run All Tests suite I have following message:
I installed node.js on windows, and I switched interpreter in configuration to it but the result after run was "Not test were found".
The text was updated successfully, but these errors were encountered: