Skip to content
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

Closed
KarelVendla opened this issue Jan 18, 2024 · 9 comments
Closed

e2e testing does not work. #720

KarelVendla opened this issue Jan 18, 2024 · 9 comments

Comments

@KarelVendla
Copy link

Environment


  • Operating System: Linux
  • Node Version: v18.18.0
  • Nuxt Version: 3.9.3
  • CLI Version: 3.10.0
  • Nitro Version: 2.8.1
  • Package Manager: [email protected]
  • Builder: -
  • User Config: devtools
  • Runtime Modules: -
  • Build Modules: -

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

@danielroe
Copy link
Member

Yes, browser testing doesn't work in stackblitz. The rest work fine.

CleanShot 2024-01-18 at 16 42 15@2x

Copy link
Contributor

Would you be able to provide a reproduction? 🙏

More info

Why 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 needs reproduction labeled issues don't receive any substantial activity (e.g., new comments featuring a reproduction link), we'll close them. That's not because we don't care! At any point, feel free to comment with a reproduction and we'll reopen it.

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
👉 https://stackblitz.com/github/nuxt/test-utils/tree/main/examples/app-jest
👉 https://stackblitz.com/github/nuxt/test-utils/tree/main/examples/module

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:

@KarelVendla
Copy link
Author

KarelVendla commented Jan 19, 2024

I ran the same exact reproduction and it took me forever?
Capture

I am using Latest Brave browser if that should make ANY difference.

@KarelVendla
Copy link
Author

KarelVendla commented Jan 19, 2024

I also ran the same reproduction on Firefox. It went a lot faster. It seems the tests completed, but it still failed.
Capture

@KarelVendla
Copy link
Author

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
Error: Worker terminated due to reaching memory limit: JS heap out of memory
or a hookTimeout

@danielroe
Copy link
Member

Would you provide a reproduction? 🙏

@KarelVendla
Copy link
Author

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 there is something else that is bothering it within our project that we haven't been able to figure out ..
So to conclude: We need to reconfigure and go over our project and find out the bottlenecks that are causing it.

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.

@danielroe
Copy link
Member

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.

@KarelVendla
Copy link
Author

Ah I see makes sense then.

@danielroe danielroe closed this as not planned Won't fix, can't repro, duplicate, stale Jan 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants