Run Jest inside sub-folder

I’m getting this error when trying to watch jest: command 'extension.jest.startJest' not found

So, after I installed the extension, nothing happens:

[Domiii]

Also having that problem. Jest Debug Console says:

Exception raised: Process failed: spawn jest ENOENT

Took me a while, but I finally figured it out:

Final solution

1. Create new runJest.sh file (in workspace root)
2. In my case, it contains: cd relative/path/to/project && npm test # NOTE: path contains package.jsonand have atest script defined
3. In VSCode’s settings.json, add: "jest.pathToJest": "sh runJest.sh"
4. Runs super smooth!

Making the Debugger work as well

When pressing “Debug” next to a test, things still error out, so what to do?

As they point out in “How to I debug tests?”, you need to add a custom test runner config in launch.json which MUST contain name: "vscode-jest-tests". I added this (and it works!!):

{
	"type": "node",
	"request": "launch",
	"name": "vscode-jest-tests",
	"program": "${workspaceRoot}/projects/todomvc/examples/vanilla-es6/node_modules/jest/bin/jest.js",
	"cwd": "${workspaceRoot}/projects/todomvc/examples/vanilla-es6",
	"args": [
		"--i",
		"--config",
		"jest.config.js"
	]
}

(NOTE: This even works on Windows if you have Cygwin installed and properly configured)

Problem Solving Process

1. The official vscode-jest troubleshooting guide tells you to set your workspace’s jest.pathToJest setting, however there is no documentation on how its supposed to work.
2. Looked at the source code and saw one special case returning npm test --, realizing it’s actually ill-named: it’s a command-line/shell command and not a path.
   • Turns out that jest from the error message (spawn jest ENOENT) refers to the value of pathToJest.
3. First I tried (in my sample project): "jest.pathToJest": "cd projects/todomvc/examples/vanilla-es6/ && npm test".
   • No dice. It cannot handle chained commands. This post probably would fix that.
   • Also note that VSC project variables/macros (such as ${workspaceFolder}) won’t be recognized (at least it did not when I tried, might just be a temporary bug)
4. Finally came up with final solution mentioned above.

[luizbon]

After the last update, still not working for me. 😦