-
Notifications
You must be signed in to change notification settings - Fork 85
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
e2e testing does not work. #720
Comments
Would you be able to provide a reproduction? 🙏 More infoWhy do I need to provide a reproduction?Reproductions make it possible for us to triage and fix issues quickly with a relatively small team. It helps us discover the source of the problem, and also can reveal assumptions you or we might be making. What will happen?If you've provided a reproduction, we'll remove the label and try to reproduce the issue. If we can, we'll mark it as a bug and prioritise it based on its severity and how many people we think it might affect. If How can I create a reproduction?We have a couple of templates for starting with a minimal reproduction: 👉 https://stackblitz.com/github/nuxt/test-utils/tree/main/examples/app-vitest A public GitHub repository is also perfect. 👌 Please ensure that the reproduction is as minimal as possible. See more details in our guide. You might also find these other articles interesting and/or helpful: |
But the real problem in my case is that when for example I try to use the browser e2e test in my local project it also stalls and throws an error |
Would you provide a reproduction? 🙏 |
After debugging our local project that ran into this heap out of memory problem we found out that using i18n with 20 locales just doesn't cut it for e2e tests on a windows machine. The lazy loading doesn't seem to really work and all the locales are being loaded into the system on setup. We brought the locale count down to 2 for testing and we also turned off jit which shaved of about 20 seconds of the initial 100 second test time .. But the thing that most surprises me is the fact that stackblitz results vary from computer to computer?? I am getting 164 second duration on stackblitz for the default test example. |
The key thing about stackblitz is that it's running in your browser so it will be constrained by your own system's memory limits, etc. |
Ah I see makes sense then. |
Environment
Reproduction
https://stackblitz.com/github/nuxt/test-utils/tree/main/examples/app-vitest
Describe the bug
The default e2e app-vitest example does not work. It stalls on beforeAll hook.
Error: Hook timed out in 120000ms. If this is a long-running hook, pass a timeout value as the last argument or configure it globally with "hookTimeout".
Additional context
No response
Logs
No response
The text was updated successfully, but these errors were encountered: