-
Notifications
You must be signed in to change notification settings - Fork 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
E2E test: Only expand the post summary section if it exists since the summary section will no longer be expansible #90736
Conversation
Jetpack Cloud live (direct link)
Automattic for Agencies live (direct link)
|
This PR does not affect the size of JS and CSS bundles shipped to the user's browser. Generated by performance advisor bot at iscalypsofastyet.com. |
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.
This works as expected 👍 I left one inline remark where I'll leave the decision to you, @olaseni.
Moreover, for the testing instructions, it looks like the environment variable should be VIEWPORT_NAME
and not VIEWPORT
.
* | ||
* @param {string} name Name of section to be expanded. | ||
*/ | ||
async expandSectionIfExists( name: string ): Promise< void > { |
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.
Not saying this approach is wrong, but I'm still curious if you considered adding something like an expandSummary
method for this specific case? I'm guessing we don't foresee any specific opportunities to reuse expandSectionIfExists
, and having a dedicated expandSummary
method might clarify that it can be removed in the future.
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.
but I'm still curious if you considered adding something like an expandSummary method for this specific case?
Sounds more to-the-point. I like it.
Instructions updated. I keep pasting those instructions around with little adjustments because there are mostly similar. I must have missed it in one of those instances. |
…ost-summary-that-is-no-longer-collapsible
This PR modifies the release build for the following Calypso Apps: For info about this notification, see here: PCYsg-OT6-p2
To test WordPress.com changes, run |
GB is making some new adjustments. See this tracking issue for more context.
At this point, in this commit and PR, the
Summary
section has been slightly re-imagined and is no longer expansible.To this end, the concerned e2e tests will be slightly adjusted as the atomic nightlies are beginning to fail. We'll check the existence of that section before we attempt to expand it. This fixes the issue temporarily. Eventually the line to expand that section should be removed in the future.
Testing instructions
Running e2e tests for Calypso