-
-
Notifications
You must be signed in to change notification settings - Fork 512
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
Slow pending with cypress #1391
Comments
Hi @iamyoki, I've had a crack attempting to re-create the bug from cloning your repository branch and installing the deps and then running the 1-intro.cy.js followed by a re-run (selecting the e2e testing type and Chrome through Cypress). Unfortunately, I wasn't able to encounter a slow execution like you described as the second run was also pretty quick like the first. Is it possible that I'm missing some steps or there are some differences in configuration and the like? I'm using the latest msw version with node v16.17.0, and I'm using a Mac with M1. |
@HeVictor Thank you for respond,I'll check again. |
No updates for about a year, I will consider this issue not reproducible. MSW doesn't do anything special to affect the response load times. If they take too much time, I suggest investigating that in your app/test setup. Start from the "Timings" tab in the Network to see what is taking that time. That can be a good first clue. Update all the dependencies to their latest versions before doing any debugging. Good luck! |
Prerequisites
Environment check
msw
versionBrowsers
Chromium (Chrome, Brave, etc.)
Reproduction repository
https://github.com/QhlabTeam/cra-template-qhlab/tree/msw-cypress-slow-issue
Reproduction steps
Clone
Install
Run cypress
Run e2e
Current behavior
Since the second re-run e2e test, it becomes very slow pending js chunks due to msw serviceworker
Expected behavior
Should be normal like the first time e2e runs.
The text was updated successfully, but these errors were encountered: