We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Add a flag like runInBand
runInBand
https://jestjs.io/docs/troubleshooting#tests-are-failing-and-you-dont-know-why
The text was updated successfully, but these errors were encountered:
@sirenkovladd, can you help me on this idea?
With isolated processes, I have the advantage of allowing .ts, .cjs, .mjs, etc. to run in the exactly same suite.
.ts
.cjs
.mjs
By removing the isolation (running the tests in the same process), it comes with some intentional limitations:
.js
CommonJS
ES Modules
In this case, the possibility of disabling isolation would be in line with your idea.
Sorry, something went wrong.
I think this is expected I think everyone who uses debug tries to execute the least number of tests (close to 1 test)
No branches or pull requests
Add a flag like
runInBand
https://jestjs.io/docs/troubleshooting#tests-are-failing-and-you-dont-know-why
The text was updated successfully, but these errors were encountered: