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
[Bug]: runInBand not respected via config file #14855
Comments
I perceive this as a feature request, as it implies the inclusion of a new field. Nevertheless, I've opened the PR #14857 to incorporate this new field into the configuration file. |
cool, thanks |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 30 days. |
This issue was closed because it has been stalled for 30 days with no activity. Please open a new issue if the issue is still relevant, linking to this one. |
1 similar comment
This issue was closed because it has been stalled for 30 days with no activity. Please open a new issue if the issue is still relevant, linking to this one. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Version
29.7.0
Steps to reproduce
"runInBand": true
to your config file (for example jest.config.cjs)Expected behavior
For
runInBand
to be respected when provided to the configActual behavior
Additional context
runInBand only works as cli argument. It is also not present in the docs for config files: https://jestjs.io/docs/configuration#workerthreads
Other people have observed this as well: https://stackoverflow.com/a/67935087/4417769
The workaround is to use
"maxWorkers": 1
Environment
The text was updated successfully, but these errors were encountered: