-
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
Performance tests: update selectors in site editor pattern loading tests #59259
Conversation
…e HTML structure. Updating performance tests to find new elements.
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. |
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.
Great catch — this looks like it matches the current state of things now 👍
LGTM once it's all green ✅
Size Change: 0 B Total Size: 1.7 MB ℹ️ View Unchanged
|
Just updated the milestone to GB 17.8 and added the backport label, as I think this PR will likely need to be cherry picked for the GB release branch in order for its tests to pass. CC: @creativecoder for visibility. |
Thanks for tracking this down ❤️ |
Thank you, @ramonjd! Unfortunately, this only partially solves this issue. The tests are still failing on Possible solutions:
cc @youknowriad |
Thanks @Mamaduka I was just wondering that.. 😄
The latter sounds like a neat solution if it doesn't affect stats? I can prep something. |
This commit makes the test backwards compatible until the performance tests base commit is updated.
The problem with updating the base branch is that it has the potential to create a small jump in the graphs, so I think we shouldn't build the habit of changing it too often. If we can make the performance test work in both branch at the same time, it would be better and would allow us to compare a bigger range of branches using the manual perf tests if needed. |
…ible (#59266) * Update Performance tests base branch after #59259 This commit makes the test backwards compatible until the performance tests base commit is updated. * use locator Co-authored-by: ramonjd <ramonopoly@git.wordpress.org> Co-authored-by: youknowriad <youknowriad@git.wordpress.org> Co-authored-by: Mamaduka <mamaduka@git.wordpress.org>
…e HTML structure. (#59259) Updating performance tests to find new elements. Co-authored-by: ramonjd <ramonopoly@git.wordpress.org> Co-authored-by: andrewserong <andrewserong@git.wordpress.org>
I just cherry-picked this PR to the release/17.8 branch to get it included in the next release: 7665bdd |
…ible (#59266) * Update Performance tests base branch after #59259 This commit makes the test backwards compatible until the performance tests base commit is updated. * use locator Co-authored-by: ramonjd <ramonopoly@git.wordpress.org> Co-authored-by: youknowriad <youknowriad@git.wordpress.org> Co-authored-by: Mamaduka <mamaduka@git.wordpress.org>
…e HTML structure. (#59259) Updating performance tests to find new elements. Co-authored-by: ramonjd <ramonopoly@git.wordpress.org> Co-authored-by: andrewserong <andrewserong@git.wordpress.org>
…ible (#59266) * Update Performance tests base branch after #59259 This commit makes the test backwards compatible until the performance tests base commit is updated. * use locator Co-authored-by: ramonjd <ramonopoly@git.wordpress.org> Co-authored-by: youknowriad <youknowriad@git.wordpress.org> Co-authored-by: Mamaduka <mamaduka@git.wordpress.org>
…e HTML structure. (#59259) Updating performance tests to find new elements. Co-authored-by: ramonjd <ramonopoly@git.wordpress.org> Co-authored-by: andrewserong <andrewserong@git.wordpress.org>
…ible (#59266) * Update Performance tests base branch after #59259 This commit makes the test backwards compatible until the performance tests base commit is updated. * use locator Co-authored-by: ramonjd <ramonopoly@git.wordpress.org> Co-authored-by: youknowriad <youknowriad@git.wordpress.org> Co-authored-by: Mamaduka <mamaduka@git.wordpress.org>
#55091 updated the way templates can be replaced in the site editor, changing some of the HTML structure, namely removing the replace template button in
sidebar-edit-mode/template-panel/replace-template-button.js
with a "transform into" list.This PR just updates the performance tests to find the new elements.
Testing
Wait for 🟢 and 🙏🏻
npx playwright test --config test/performance/playwright.config.ts test/performance/specs/site-editor.spec.js