EarlGrey's synchronization gets blocked in SCPaymentsEditorTestCase.testNavigationByTappingReturn |
||
Issue descriptionOn iPad, in SCPaymentsEditorTestCase.testNavigationByTappingReturn, when the focus moves to the Postal Code field, the first call to GREYAssertTrue in AssertTextFieldWithAccessibilityIDIsFirstResponder() times out. A temporary solution was to disable EarlGrey's synchronization. Investigate what is causing this.
,
Oct 3 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/fe2895e63ab48f2a1efffd7e3544fc9beb89fa61 commit fe2895e63ab48f2a1efffd7e3544fc9beb89fa61 Author: Mohamad Ahmadi <mahmadi@chromium.org> Date: Tue Oct 03 18:41:13 2017 [PR] Enables SCPaymentsEditorTestCase/testNavigationByTappingReturn Enables the test by fixing two issues for iPad devices: - Fixes the test for iPad9 by using a grey_anyOf() matcher for the return button's accessibility identifier matcher instead of iOS version check. - Fixes the flakiness for iPad10 by modifying the test to be more stable so that it doesn't require disabling EarlGrey's synchronization. Bug: 769464 , 768864 Change-Id: Iccab74d15c65951c891576a9ed3ca917cce531a9 Reviewed-on: https://chromium-review.googlesource.com/695819 Reviewed-by: edchin <edchin@chromium.org> Commit-Queue: Moe Ahmadi <mahmadi@chromium.org> Cr-Commit-Position: refs/heads/master@{#506118} [modify] https://crrev.com/fe2895e63ab48f2a1efffd7e3544fc9beb89fa61/ios/showcase/payments/sc_payments_editor_egtest.mm
,
Oct 3 2017
|
||
►
Sign in to add a comment |
||
Comment 1 by mahmadi@chromium.org
, Oct 2 2017