Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[v4] What else has been changed in testing ?
See original GitHub issueI upgraded react-scripts in my project from version 3.4.x to 4.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 to true by default in the Jest config! (hmm, this isn’t expected), so, I added:
"resetMocks": false,
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,
"test": "react-scripts test --coverage --watchAll=true",
runs only 118 (25 suites)!
Thanks!
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Can you please try setting
watchAlltofalseand let me know if that changes anything?I am getting: “Nothing was returned from render”