[Testing] Fix for flaky UITests in CI - 3 #33178
Open
+31
−11
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.
This pull request improves the reliability and accuracy of UI tests by addressing test flakiness, enhancing assertions, and refining test logic. The main focus is on making tests more robust across different platforms (especially in CI environments) and ensuring UI behavior is correctly validated.
Test reliability improvements:
GesturesSenderIsView()on Mac Catalyst to reduce test flakiness in CI environments.TapThenDoubleTap()to both Android and iOS platforms, not just Android, to handle potential flakiness.Test accuracy and validation enhancements:
ModalPageMarginCorrectAfterKeyboardOpens()by capturing and asserting the position of anEntrybefore and after keyboard appearance/dismissal, ensuring the UI remains visible and returns to its original state.TextInEditorShouldScroll()to use a more precise scroll command (ScrollStrategy.GesturewithwithInertia: false), improving test consistency.