[Bug]: Jest and babel-jest 27.3.0v update gives error on running tests
See original GitHub issueVersion
27.3.0
Steps to reproduce
Updated the jest and babel-jest versions to 27.3.0v and gives below error,
Expected behavior
Should be able to run my existing tests without any error
Actual behavior
Gives above mentioned error
Additional context
No response
Environment
System:
OS: Windows 10 10.0.19043
CPU: (12) x64 Intel(R) Core(TM) i7-10750H CPU @ 2.60GHz
Binaries:
Node: 16.2.0 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.10 - ~\AppData\Roaming\npm\yarn.CMD
npm: 7.13.0 - C:\Program Files\nodejs\npm.CMD
npmPackages:
jest: ^27.3.0 => 27.3.0
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (2 by maintainers)
Top Results From Across the Web
Exceeded timeout of 5000 ms for a test · Issue #11607 - GitHub
I am upgrading jest from v1.4.3 --> 2+, with chromedriver version 91+. I have started getting this issue: thrown: "Exceeded timeout of 5000...
Read more >Issue with babel-jest dependency when running npm start in a ...
I get the following error/output/log. I have walked through all of the suggested steps. The only thing that works is the SKIP_PREFLIGHT_CHECK= ...
Read more >Jest 28: Shedding weight and improving compatibility
Jest 28 is finally here, and it comes with some long requested features such as support for sharding a test run across multiple...
Read more >jest | Yarn - Package Manager
Instant Feedback: Failed tests run first. Fast interactive mode can switch between running all tests or only test files related to changed files....
Read more >How to resolve create-react-app babel-jest Error. - Medium
It is likely not a bug in Create React App, but something you need to fix locally. ... Try running npm ls babel-jest...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@mrazauskas Thanks, removing identity-obj-proxy and adding testEnvironment worked for me
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.