Size Change: +960 B (0%)

Total Size: 1.32 MB

_{compressed-size-action}

Looks like this test needs work since the page list block has changed :D

@kevin940726 I've tried to wait on specific network requests. But every time I try running these tests the isVisible expect always timesout.

I looked at the artifacts provided by the test runner and no matter what I do the Page List block only becomes visible in the editor after the isVisible check runs. I even tried adding a 10s timeout!

I'm a bit stuck at this point. Any help or advice would be much appreciated.

Flaky tests detected in 491a297.
Some tests passed with failed attempts. The failures may not be related to this commit but are still reported for visibility. See the documentation for more information.

🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/3868144494
📝 Reported issues:

• [Flaky Test] should always expand single line selection #39787 in specs/editor/various/multi-block-selection.test.js
• [Flaky Test] should move the blocks up #39782 in specs/editor/various/block-editor-keyboard-shortcuts.test.js

But every time I try running these tests the isVisible expect always timesout.

Thanks for the ping! I believe it's because we didn't use editor.canvas to access the element. Since now the post editor is iframed, we have to modify our selector to select from the iframe canvas. In order to do that, we also have to initiate the editor utils with the hasIframe option set to true. It's a bit tedious now that almost every editor is iframed though. I started a separate discussion about that in #40815 (comment).

I hope it's okay for me to push the change directly on this branch :).

Ok I'm happy with the structure and intent of this test. Requesting final review(s).