-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Patterns: add a new spec for for adding an unsynced pattern #54892
Conversation
Size Change: -22 B (0%) Total Size: 1.62 MB
ℹ️ View Unchanged
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice! I left some suggestions that would be good to get in as the first series of the tests.
Flaky tests detected in 8c3a829. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/6335401289
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me!
Co-authored-by: Kai Hao <kevin830726@gmail.com>
} ) | ||
); | ||
before.forEach( ( block ) => { | ||
delete block.clientId; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice, that is much simpler 🤦
What?
Adds an e2e spec for adding an unsynced pattern in the post editor.
Why?
To try and guard against future regressions like #54804.
How?
Adds a new spec that goes through the flow of adding an unsynced pattern in the post editor, checking that it is not mistakingly added as synced, and checking that it is then available in the inserter, and gets inserted as a plain block.
Testing Instructions
npm run test:e2e:playwright specs/editor/various/unsynced-pattern.spec.js