Lachlan Miller

Headless (well "run mode" where you run all specs) execution for Component Testing will improve significantly (up to ~50% on large code bases, improvement linear based on # of specs)...

Finishing running your project before/after: 205 specs Before: 42m After: 4m Final numbers (run on my Macbook arm64) ``` # experimentalSingleTabRunMode: false yarn cy:run-ct --config video=false --browser chrome 17.88s user...

Great, I hope we can ship the experimental flag with 10.5. If it goes smoothly, we can make this the default in the future. 🤞 Keep your eyes on https://github.com/cypress-io/cypress/pull/23104...

Hmm that's odd, I wonder why the CDP real-events are failing 🤔 Glad the experiment is helping - if it goes well over the next few weeks and no-one reports...

I think I misunderstood this issue when it was mentioned (iirc in another issue, not sure if by a different user). To clarify you are writing E2E tests against an...

Okay, I think I understand what you are describing now. Just to clarify: > If you build the app and run the tests against the production build (not the version...

> I'm 99% sure this is a Vite-but-only-when-used-in-development-mode issue This is useful, and I think based on what you've suggested, you are correct. > Please let me know if there's...

> Vite is a build tool that enables faster development by re-compiling only the changed files on each save, and using a simple development server that supports hot module replacement...

I think these two might be related: https://github.com/cypress-io/cypress/issues/22868 Projects that serve lots of assets (100s of network requests) take a long time to load. It's not obvious normally when you...

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 via a proxy layer we...