-
Notifications
You must be signed in to change notification settings - Fork 4.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
Mobile - Update editor initial HTML test for iOS and update Appium #44732
Conversation
Size Change: 0 B Total Size: 1.27 MB ℹ️ View Unchanged
|
f4f770a
to
c98347f
Compare
…ition helper instead of a manual delay
aa51fdc
to
fdd7dd7
Compare
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.
LGMT 🎊 ! Awesome work @geriux 🏅 !
After running the E2E tests three times all of them succeed ✅ , so looks like they're less flaky than before 🤞 .
React Native E2E Tests (Android) | React Native E2E Tests (iOS) |
---|---|
@@ -16,22 +19,10 @@ describe( 'Gutenberg Editor Blocks test', () => { | |||
lastBlockAccessibilityLabel | |||
); | |||
} else { | |||
lastBlockElement = await editorPage.getLastElementByXPath( | |||
lastBlockAccessibilityLabel | |||
lastBlockElement = await editorPage.getBlockAtPosition( |
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 noticed that getBlockAtPosition
has an option to auto-scroll to the element, so we could use it also in the if ( isAndroid() )
case to simplify the test, wdyt?
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.
Thanks for the suggestion! I tried it but it is not working for this test, it begins to scroll down but then it stops just returning:
"//android.view.ViewGroup[contains(@content-desc, "Paragraph Block. Row 30")]" is still not visible after 25 retries!
I'm going to merge this so we can see how it performs in trunk, if there's any tweaks needed I could investigate it further to unify it for both platforms.
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.
Thanks for the suggestion! I tried it but it is not working for this test, it begins to scroll down but then it stops just returning:
"//android.view.ViewGroup[contains(@content-desc, "Paragraph Block. Row 30")]" is still not visible after 25 retries!
Ah, it's a shame that didn't work. Thanks for checking it 🙇 !
I'm going to merge this so we can see how it performs in trunk, if there's any tweaks needed I could investigate it further to unify it for both platforms.
Sure, my comment was just a suggestion, we can explore in the future enhancements to this test case.
Related PRs:
What?
It updates the initial HTML test for iOS using the
getBlockAtPosition
helper instead of manually adding retry logic when trying to locate the last block.Why?
There were quite a few failures lately related to the iOS test.
How?
First, it updates the test to use
getBlockAtPosition
which has the latest code improvements to find a block in E2E tests.It also updates:
1.22.3
iPhone 13
15.4
For Android:
11.0
1.22.1
(It doesn't support1.22.3
yet)28
. I tried different approaches but it would fail to boot the emulator, it looks like the machine it uses it's too slow and it times out.Dependabot updates that got merged before this PR:
Testing Instructions
Circle CI should pass, maybe try restarting the jobs to see if they succeed again.
Gutenberg Mobile PRs should also pass, including full test checks.
Screenshots or screencast
N/A