[Testing] Resolved bunch of Android UI Test random failures in CI. #27066
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.
Description of Change
Fixes for Android UI Tests were failing frequently in CI due to unexpected interference from the notification panel.
Solution
Implemented a fix by calling
App.Back()
within theFixtureSetup
method. This approach ensures that the navigation panel is dismissed before resetting the App while facing any exception on FixtureSetup method, providing a consistent starting point for test after the first FixtureSetup failure.Note: The fix is also applied to the existing common base class for Controls Gallery tests. and modified the base class for each control tests as
CoreGalleryBasePageTests.