-
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
Improve Site Editor performance tests #48138
Merged
Merged
Changes from all commits
Commits
Show all changes
23 commits
Select commit
Hold shift + click to select a range
184bf0d
Fix site editor performance tests
WunderBart 01bc9e2
Restore some comments
WunderBart 3dbc1fe
Try uploading artifacts to see why CI is failing
WunderBart 1a1298c
try setting failure breakpoints to get screenshots
WunderBart 835f3c6
Try checking if the test post is being saved correctly
WunderBart f4a1a9f
Clear local storage in pageSetup
WunderBart f2f52a1
Try wait longer for the SE
WunderBart 0ab0c95
Clean up a few bits
WunderBart dee6e71
Add missing path param
WunderBart fbe4439
Remove temp code
WunderBart f84146c
Fix LS clearing
WunderBart edd93b6
Add more tweaks
WunderBart 4a549fc
Revert "Try uploading artifacts to see why CI is failing"
WunderBart 91bdc33
Improve wording
WunderBart 3781e85
Remove obsolete path param
WunderBart 10d7c04
Add `sequence` util
WunderBart 8486b48
Hold the PostContent block render until userCanEdit status loaded
WunderBart 6dcc933
Don't use hacky selectors
WunderBart a5899a4
Merge remote-tracking branch 'origin' into fix/site-editor-performanc…
WunderBart cc09c6f
Move `sequence()` to `utils.js`
WunderBart 5623f43
Wait for any block for the `firstBlock` load time
WunderBart a0f60cb
Merge remote-tracking branch 'origin' into fix/site-editor-performanc…
WunderBart 3da31c0
Use single parent `describe` for consistency
WunderBart File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
results
object contains data for bothLoading
andTyping
tests, so let's write the file in theafterAll
hook instead of the end of theTyping
test.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.
is storing this file alongside the sourcecode the optimal choice here? I know I was confused when first storing results files as artifacts because of the directory structure. would we want to move these instead to our relatively-new
__test-results
directory?we could consider some kind of
TEST_RESULTS_BASE_DIR
ENV
to hold the base path if we wanted to avoid doing path-math everywhere: running in CI vs. locally in Docker vs. locally without Docker…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.
Agreed, we should be able to pass the
__test-results
path as an env variable and save directly there. Will give it a try.edit:
OTOH, let's leave that for a follow-up PR. It touches all the other perf tests and I wanted to make this PR about the Site Editor ones only.
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've drafted the refactor in #48684, but I'm not sure how to handle the "locally without docker" situation. I think it still makes the most sense (as it's most convenient) to store alongside the sourcecode when running e.g. via
npm run test:performance -- site-editor
.Let me know if that makes sense to you.
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 main thing about colocating with sourcecode is that it leaves its mess distributed around the project. at least when creating a project-root-level
__test-results
directory it's easy to wipe that out in one command.see for example challenges with the distributed
build
,build-styles
,build-modules
, andbuild-types
directories in each package directory.I'll add further remarks in the linked PR.
thanks! ✋