Symlink Path Resolution

[cenk1cenk2]

I have a weird problem, done some searches in the issues but could not find something closer to this.

My working directory is a symlink to another place. When it tries to resolve the pattern it uses the symlinked path while it searches for it inside the original directory.

jestrunner is utilized through SSH-Remote plugin to another server in vscode-insiders 1.48.0 version. Everything else seems okay for it to run.

If there is already an issue open for this I am terribly sorry.

[fermmm]

When you opened your project in vscode, if you navigated to the project folder using a simlink/link then your project path will be the "link" path and not the "real" path and the extension doesn't work because it executes Jest with the path you navigated when opening the project and Jest does not support link paths. Then you see an error like: No tests found, exiting with code 1. They have an issue opened with this problem: jestjs/jest#7549

Workaround:

Open your project folder again in vscode browsing the real path to the folder without simlinks.

How could this extension fix this issue:

Running this command converts a link path into a real path:
readlink -f <link path>
This could be used before calling jest and fix the issue.

[cenk1cenk2]

Thank you for the workaround. I will close this issue since it is more related to jest then this plugin.