jest
jest copied to clipboard
jestjs
[Bug]: Scripts with syntax errors are ignored by --onlyFailures
Version
29.7.0
Steps to reproduce
- Have a test script with a syntax error in it
- Execute your tests and observe a test is reported as having failed
- Execute the tests again with
jest -f, and observe the output is
No failed test found.
Expected behavior
I would expect to be able to fix my script and rerun it with jest -f
Actual behavior
Executing jest -f yields
No failed test found.
Additional context
No response
Environment
System:
OS: macOS 15.1
CPU: (10) arm64 Apple M1 Pro
Binaries:
Node: 20.12.0 - ~/.nvm/versions/node/v20.12.0/bin/node
Yarn: 1.22.19 - /opt/homebrew/bin/yarn
npm: 10.9.0 - ~/.nvm/versions/node/v20.12.0/bin/npm
pnpm: 8.5.1 - /opt/homebrew/bin/pnpm
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.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
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 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 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 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 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 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 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 has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.