RTC: Fix 'networkidle' and other e2e tests that are flaky#76214
RTC: Fix 'networkidle' and other e2e tests that are flaky#76214alecgeatches merged 3 commits intotrunkfrom
Conversation
|
Size Change: 0 B Total Size: 6.89 MB ℹ️ View Unchanged
|
|
Flaky tests detected in 550d31b. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/22780031201
|
0d683fa to
94b17f8
Compare
…with RTC in the editor
94b17f8 to
abe4ee8
Compare
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
What?
Remove
await page.waitForLoadState( 'networkidle' )from end-to-end tests.Why?
Now that real-time collaboration is turned on by default, the
networkidlestate is a lot more flaky. Once RTC has connected via the default transport, it's constantly sendingPOST /wp-sync/v1/updatecalls, meaning that we may not hit a period ofnetworkidleduring tests. These tests will eventually time out.How?
The only two
networkidleuses in e2e tests appear to be workarounds for previous flaky results. We've tried to use another method and await something else instead in both cases.Testing Instructions