-
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
[RNMobile] Look for newly available blocks too during E2E tests #35948
Conversation
Size Change: 0 B Total Size: 1.07 MB ℹ️ View Unchanged
|
👋 @dcalhoun ! Added you as a reviewer since you have probably the best insight in the "new block" badge work. Let me know if the approach here makes sense to you, open to other approaches too. Thanks! |
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 approach looks good to me. Thank you for fixing this! 🚀
It is unfortunate that Appium cannot match partial accessibility IDs and that Xpath queries are so slow, as either one of those options would likely make the code simpler.
Description
Updates the native mobile E2E "find block in inserter" method to account for newly available blocks too, since those have a slightly different accessibility ID.
After we bumped the mobile Editor Onboarding features to 100% rollout, some E2E tests started failing on
develop
of gutenberg-mobile due to the "newly available" marked blocks escaping the search methods.Related PRs
How has this been tested?
gutenberg-editor-search.test.js
testsTypes of changes
Update the
findBlockButton()
method to search for both versions of the block name${ blockName } block
and${ blockName } block, newly available
.Checklist:
*.native.js
files for terms that need renaming or removal).