E2E: Fix draggable block tests#43739
Conversation
|
Size Change: -17 B (0%) Total Size: 1.25 MB
ℹ️ View Unchanged
|
ciampo
left a comment
There was a problem hiding this comment.
Changes LGTM!
Let's hope that this change is enough to fix the test flakiness.
| } from '@wordpress/e2e-test-utils'; | ||
|
|
||
| describe( 'Draggable block', () => { | ||
| // Tests don't seem to pass if beforeAll and afterAll are used. |
There was a problem hiding this comment.
Reminder to remove this comment before merging :)
8877a24 to
7ec02bf
Compare
|
It still seems to be failing. The test seems to not add any blocks at all, so I wonder why that is. It currently follows the same flow as many other tests by using the Perhaps there's an issue with |
Until recently, that test was pressing The main issue here, as you also said, is that the snapshot being returned doesn't have any blocks:
A couple more interesting things that can be noted from the snapshot images taken on CI for the failed test:
Another thing that I noticed from the snapshots, is that the post ID always skip a number, i.e 151, 153, 155, 157 ... which suggest that there may be other posts created between each test? Is that because of other tests being run concurrently? In that case, could we see if running only this test spec changes anything? Or is this test spec somehow creating 2 new posts every time, instead of one (which could also explain why the new post is empty? Just a few wild guesses. |
This reverts commit 6f31f92.
|
This is now fixed by #43798 (the tests have been migrated to Playwright) |


What?
Closes #43737
This is an attempt to make the draggable block tests pass. I've noticed that before- and after- hooks were incorrectly used:
gutenberg-test-plugin-disables-the-css-animationsshould not be in the beforeEach hook, andTesting Instructions
I've re-run E2E jobs 3 times to be sure this fixes the draggable block tests.