Jest tests hanging forever with large snapshot changes
See original GitHub issueJest tests hanging forever when there have been large snapshot changes. Running jest -u
seems to fix the issue.
Reproduce by pulling down this branch and running jest
. It should sit spinning forever. Run jest -u
to fix. Subsequent calls to jest
should work.
Issue Analytics
- State:
- Created 6 years ago
- Comments:10 (4 by maintainers)
Top Results From Across the Web
node.js - jest hangs indefinitely, runs no tests - Stack Overflow
I have discovered a workaround which is to run using the --runInBand flag, which just runs tests in the same thread: jest --runInBand....
Read more >How to Stop Jest Tests from Hanging in Angular | by Paul Kim
Jest test hangs, hanging, stuck, never finishes, not running, won't stop. An article to stop hanging Jest tests in an Angular project.
Read more >Make Your Jest Tests up to 20% Faster by Changing a Single ...
TL;DR. When you have Jest as your test runner, passing the --maxWorkers=50% option will make the tests faster in most cases.
Read more >Snapshot Testing - Jest
Snapshot tests are a very useful tool whenever you want to make sure your UI does not change unexpectedly.
Read more >Changelog - Cypress Documentation
This change aligns Cypress' cookie rules with the browser cookie rules. ... but can impact spec isolation and reliability on large test suites....
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
Hi @pedrottimark , We are also facing the same issue. Are there any updates? Did you get a chance to open a pull request?
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.