E2E test: Move check for the Premium Content block from Earn to Grow #49642
Conversation
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
matticbot
added
the
[Status] Needs Review
|
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. |
noahtallen
approved these changes
Feb 3, 2021
andrewserong
deleted the
update/e2e-move-premium-content-to-grow-section
branch
matticbot
removed
the
[Status] Needs Review
|
Thanks for doing this! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
With the recent move to adding the Premium Content block to Jetpack, it looks like the block has moved in the inserter from the Earn section to the Grow section, and this caused one of the e2e tests to fail. To get the e2e tests passing again, this PR updates the check to look for the Premium Content block in the Grow section.
Changes proposed in this Pull Request
Testing instructions
Related to #