miragejs | side server to build , test and share your JavaScript app | Websocket library

Hopefully i solved the problem.It was in the method which async thunk got the data.Above i used axios,but replacing just with fetch keyword it helped,so,my educationSlice now looks like this:

Provide a default value, to destructure from employees.map(({id, firstName, lastName}).

This is what the Jest documentation says about how it finds test files:

By default it looks for .js, .jsx, .ts and .tsx files inside of __tests__ folders, as well as any files with a suffix of .test or .spec (e.g. Component.test.js or Component.spec.js). It will also find files called test.js or spec.js.

Since the setupTests.js filename does not meet this criteria, Jest does not recognize it as a test file. If you rename the file to end with .test.js or move it into a __tests__ folder, Jest should be able to find it and run the test. If you need to keep the filename as is, this default behavior can be changed by setting testRegex in jest.config.js (read more about this setting here).

The setupFiles property in jest.config.js is used for setting up the environment before the tests actually run. The documentation for that setting can be found here, but it doesn't appear to be necessary to do any setup for this case based code you provided.

The problem with your code is here:

react-router v6 doesn't use RouteComponentProps anymore. Here are some links with examples on how to change route and how to use params on v6 with some links where you can find more informations:

For changing route (old history.push)

If you want to change the route after the login is successful react-router docs specify

In v6, this app should be rewritten to use the navigate API. Most of the time this means changing useHistory to useNavigate and changing the history.push or history.replace callsite.

So basically instead of having somthing like

Figured out my own issue. I had set global.window = {} in the jest.setup.js file earlier. @testing-library/react-native uses a timers.js file in which they refer to globalObj which they obtain from the following: const globalObj = typeof window === 'undefined' ? global : window;. As window was not technically undefined, globalObj was being set to {} and did not have access to global functionality.

I'm not familiar with MirageJS so I might be off, but can you use globalScript (https://stenciljs.com/docs/config) and then run your Mirage server there?

I am on the Developer Experience team at Cypress.

We have recently published a guide for CircleCI which details the solution deployed in the Cypress Real World App repo.

Normally not. However there is an issue in cypress, since v7.2: https://github.com/cypress-io/cypress/issues/16671

You can try to downgrade your cypress to 7.1 to evaluate if your performance-issue is related to this bug.