agentdon

Just came across this issue because I'm having problems with E2E tests being painfully slow. I don't have official measurements, but the tests are pretty much unusable for local dev....

Got it, thanks Lachlan! For anyone else who may be running into slow E2E tests, I opened #22968.

@rubber-duck-software Glad you mentioned the files loading one at a time and the extremely long initial start time. I'm seeing the same thing as well. However, in our case the...

@mverdaguer There's also an open issue for slow component tests [here](#22353). Not sure if you saw that or not, but it might be helpful to post the information in that...

Correct. > To clarify you are writing E2E tests against an app running in dev mode with yarn vite? I'm not exactly sure what the bottleneck is. Like @rubber-duck-software mentioned,...

Sorry, I wasn't clear in my previous message. 🙂 I'm 99% sure this is a Vite-but-only-when-used-in-development-mode issue. I only encounter this problem when running `yarn vite dev`. As you suggested,...

Before I respond to the rest of your comments, when I opened up Cypress to run things in debug mode as you suggested, I noticed that things seem to be...

Yes, `vite preview` is working properly. I also believe that there's something weird going on in the interaction between `vite dev` and Cypress. > So vite preview is working properly?...

That would make sense. > Hey @agentdon, nice instinct around trying incognito. I think the problem is we have a bottleneck in the Cypress network proxy. Basically, all requests go...

I tried this, but it unfortunately didn't work. Thanks for the suggestion though! 🙏 > Random aside, try setting NO_COMMAND_LOG > > ```javascript > e2e: { > env: { >...