-
Notifications
You must be signed in to change notification settings - Fork 4.6k
Template Activation: Update template ID format test #73629
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
Conversation
|
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. |
| await expect( saveButton ).toBeDisabled( { timeout: 5000 } ); | ||
| } | ||
|
|
||
| await expect( page.locator( 'body' ) ).not.toContainText( |
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.
I wonder if there could be another way to check if the template saved. Checking for this error seems a bit fragile, the text might change, and then this will no longer catch a regression.
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.
I tried checking for the templates API response but it kept timing out. This is what I tried:
await page.waitForResponse( ( response ) => {
return (
response.url().includes( '/wp/v2/templates' ) &&
response.status() === 200
);
} );
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.
I think in other tests, we're just checking the front-end. Maybe we can try that?
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.
I figured out how to use saveSiteEditorEntities correctly... I don't think we need to check the front end or the error text anymore, the save utility fails correctly now 😄 Fixed in 00020e7.
|
Size Change: 0 B Total Size: 2.58 MB ℹ️ View Unchanged
|
|
Flaky tests detected in 99a9019. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/19744578455
|
scruffian
left a comment
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, thanks for following up!
|
Hey, folks It seems this e2e test became very flaky since this PR got merged - #73752. |
|
Oh no, thanks @Mamaduka. Will take a look soon. |
|
Thank you, @mikachan! |
What?
Updates the template ID format test to include two edits to the template, as this is what was causing the original bug.
Why? / How?
Ensure test covers regression by including two edits to the template.
Testing Instructions