2 ms·
Not really, it was experimental and only released recently (end of last year?). You can't really build experimental features with potentially breaking changes o
by EddyTests 3y ago
Not really, it was experimental and only released recently (end of last year?). You can't really build experimental features with potentially breaking changes or even a complete removal into a CI pipeline without a lot of risk.
The main issue with Cypress handling this is, from what I understand, one browser per domain which can cause huge memory usage (which Cypress already has an issue with). Once you try parallelising multi-domain tests you run out of memory on developer laptops pretty quickly :(
But yes ultimately you are right, multi-domain is available, it's just those edge cases that get you once you go beyond simpler cases.
- lmiller1990 3y agoHi, I work on Cypress (but not the multi domain feature). I agree memory usage is an issue, I sure hope we can fix that. It's a hard problem with the frontend execution heavy model Cypress uses, along with the DOM snapshots consuming a ton of memory. There is a `experimentalMemoryManagement` feature that might be of interest to you [0]. The reason this one is experimental is the implications are not fully understood yet, and as a mature software product, we can't just throw out a big feature and "see what happens", so to speak. I understand not wanting to use experimental features, but this might be useful to your existing Cypress projects, even if you aren't using it for your new projects anymore. [0] https://docs.cypress.io/guides/references/experiments https://docs.cypress.io/guides/references/experiments
- EddyTests 3y agoThanks for the info! I’ll check it out :)