-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
E2E Tests: Add coverage for reusable blocks save button state regression #33151
E2E Tests: Add coverage for reusable blocks save button state regression #33151
Conversation
Size Change: 0 B Total Size: 1.13 MB ℹ️ View Unchanged
|
packages/e2e-tests/specs/editor/various/reusable-blocks.test.js
Outdated
Show resolved
Hide resolved
|
||
await publishPost(); | ||
|
||
// Close publish panel. |
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.
should this part of the publishPost utility?
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.
We have some tests that click the publish panel's "View Post" link right after publishing, so we'd have to modify those. If it's okay, I'd thus leave publishPost
untouched for now, in order to get this PR in without further detours :)
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.
the reusable-blocks e2e test failures seem related to change here maybe?
275ca1c
to
34398d4
Compare
e2e tests seem to pass after a rebase. I'll try to pick this up and get it ready for another round of review. |
Hmm, I can't seem to get the test to fail anymore, even when reverting the relevant changes from 127cc57 😅 |
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.
Hmm, I can't seem to get the test to fail anymore, even when reverting the relevant changes from 127cc57 😅
I guess it's because you had made another proper fix after the revert 😄
In order to make the test fail you need to make the change you were looking in the revert PR and also revert the changes you made in the fix afterwards here - that code wasn't there at the time of the regression and the revert.
I'll approve this as I could make it fail with the above but I'd like an extra sanity check Bernie 😄. Thanks!
Hah, of course! 🤦♂️ Thanks, I didn't see the forest for the trees 😅 Let the record show that reverting a6908dc and then 127cc57 (and then rebuilding Gutenberg) does indeed cause the test to fail 🥳
Thanks a lot! I'll go ahead and merge 🎉 |
Description
Adds E2E test coverage for #33072.
How has this been tested?
Verify that e2e tests pass for this branch (CI or locally).
Check the branch out locally, revert
127cc57641caacc7187608edf3e2b11382e70f84
, and rebuild Gutenberg. Verify that the newly added e2e test now fails.