Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • C create-react-app
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,547
    • Issues 1,547
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 417
    • Merge requests 417
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Meta
  • create-react-app
  • Issues
  • #9876
Closed
Open
Issue created Oct 23, 2020 by Administrator@rootContributor

[v4] What else has been changed in testing ?

Created by: MalekBouba

I 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!

Assignee
Assign to
Time tracking