Flaky end-to-end test for add section/component functionality, reproducible with network throttling

balintbrews → credited jessebaker → .

balintbrews → closed merge request !182

Ah, so this is accounting for non-react JS execution that might still be in-progress after the dom element is spotted in the iframe. That was not accounted for previously and it is happening so it's nice to have a non-ambiguous cause.

This seems like something that would be a challenge with any e2e test on this type of application - not just Cypress. Excellent work narrowing it down to a specific cause vs stuffing the files full of cautiously optimistic waiting. Approved the MR and looks like it just needs 1 more codeowner.

Automatically closed - issue fixed for 2 weeks with no activity.