-
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
DataViews: add performance test for pages #63170
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. |
Size Change: -19 B (0%) Total Size: 1.76 MB
ℹ️ View Unchanged
|
Flaky tests detected in a3dc531. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/9805167542
|
|
||
const startTime = performance.now(); | ||
|
||
await page.getByRole( 'button', { name: 'Pages' } ).click(); |
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 we should be using the "list" view. I think maybe using the "table" view would be better and we could set the url explicitly in the admin.visitSiteEditor
call as it's less fragile to changes we might do to the root page of "pages".
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.
list is also kind of tested in the "navigate" metric.
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.
Sure I changed it to start with the trash table view then. The reason for this is that we don't want to measure a complete page load.
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.
list is also kind of tested in the "navigate" metric.
Actually, I just checked this test, and it doesn't test loading the list view, it only tests selecting item from the list after it has loaded.
|
||
await page.getByRole( 'button', { name: 'Pages' } ).click(); | ||
|
||
await Promise.all( |
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.
What are we waiting for exactly here, can we add a clarifying 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.
Added one, we are waiting for all pages to load.
Co-authored-by: ellatrix <ellatrix@git.wordpress.org> Co-authored-by: youknowriad <youknowriad@git.wordpress.org>
What?
See #63151.
Adds a performance test for the pages data view (per page = 20, the default). These are just simple pages. Maybe at some point we can add featured images.
Why?
It's easier to get a sense of progress when we're measuring.
How?
See the test's code.
Testing Instructions
There should be an extra entry for
loadPages
is the performance test.Testing Instructions for Keyboard
Screenshots or screencast