You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
are you able to run jest test from command line? Only using --watchAll
how do you run your tests from command line? (for example: npm run test or node_modules/.bin/jest) pnpx jest --watchAll
Steps to Reproduce
In a monorepo using git submodules and a multi-project setup (jest.config.js in the root using the projects option to run the test suites of all packages), running Jest in watch mode (jest --watch) always errors out with something along the lines of:
Determining test suites to run...
● Test suite failed to run
fatal: ../packages/a-dependency-outside-the-submodule: '../packages/a-dependency-outside-the-submodule' is outside repository
This is a variant of a known Jest issue, and the usual workaround is to run Jest with --watchAll instead of --watch.
vscode-jest aways errors out, though, because it tries to use --watch and there is no way (that I could find) for force it to run Jest with --watchAll.
Expected Behavior
I would like to have an option to run Jest with vscode-jest using watchAll instead of watch, or having the extension detect this kind of error and behave accordingly.
The text was updated successfully, but these errors were encountered:
looks like there is code attempted to detect such situation here, is that not working for your use case or maybe the regex is outdated or too rigid... want to give it a try to fix it?
@connectdotz I took a super quick stab at it. I see the build failing, but from the log it seems like it is Danger having some trouble posting its comment (and is lying about the email addresses not being verified) – any insight about that?
Environment
node -v
: v12.13.1npm -v
: 6.13.6Prerequisite
--watchAll
npm run test
ornode_modules/.bin/jest
)pnpx jest --watchAll
Steps to Reproduce
In a monorepo using git submodules and a multi-project setup (
jest.config.js
in the root using theprojects
option to run the test suites of all packages), running Jest in watch mode (jest --watch
) always errors out with something along the lines of:This is a variant of a known Jest issue, and the usual workaround is to run Jest with
--watchAll
instead of--watch
.vscode-jest aways errors out, though, because it tries to use
--watch
and there is no way (that I could find) for force it to run Jest with--watchAll
.Expected Behavior
I would like to have an option to run Jest with vscode-jest using
watchAll
instead ofwatch
, or having the extension detect this kind of error and behave accordingly.The text was updated successfully, but these errors were encountered: