-
-
Notifications
You must be signed in to change notification settings - Fork 26.9k
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
[v4] What else has been changed in testing ? #9876
Comments
Can you please try setting |
It works fine with |
I am getting: "Nothing was returned from render" |
@chrkaatz maybe is related to this issue in jest? |
This issue has been automatically marked as stale because it has not had any recent activity. It will be closed in 5 days if no further activity occurs. |
I upgraded
react-scripts
in my project from version3.4.x
to4.0.0
and testing isn't like before.I read the changelog, you said that you've upgraded to Jest 26 and now set
resetMocks
totrue
by default in the Jest config! (hmm, this isn't expected), so, I added:to make my tests work again. I fixed some other new
Eslint
warning (and that's okay)...BUT, Now it covers only a part of the test suits!
I have 420 tests (551 suites) in the project,
runs only 118 (25 suites)!
Thanks!
The text was updated successfully, but these errors were encountered: