You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm facing problem with super slow test running in jest.
I have noticed, that one simple test can take about 2 min.
Next time it will work faster, but if I change code in the test file, I have to wait again about 2 min.
I tried jest-cli version 0.9 and 0.10: no difference, both slow.
Also when I run test with --watch, it stuck.
This is most definitely not normal and I'm unable to reproduce this locally. If this happens only on the first run, it most likely means that your babel configuration is messed up and that babel is doing something that it should not. On the first run, babel transforms all files under test.
To prove that this is indeed a babel problem, I recommend doing rm -rf node_modules/babel-jest and then running Jest – if the test runs significantly faster (less than 1s as expected), it is definitely a babel problem. Your test file doesn't currently seem to use any babel transforms either.
I'm closing this because it's unlikely that it is a Jest issue, but happy to reopen if it turns out to be related to Jest.
Just for the history: the reason was in the slow hard drive.
After "million" experiments with different node modules (installation/deinstallation), my drive was completely fragmented. After defragmentation everything works quickly.
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.