Closed Bug 1498249 Opened 7 years ago Closed 7 years ago

XCUITests: Cannot get from BrowserTab to TabTray intermittent error

Categories

(Firefox for iOS :: Build & Test, enhancement)

Other
iOS
enhancement
Not set
normal

Tracking

()

RESOLVED FIXED
Tracking Status
fxios + ---

People

(Reporter: isabel_rios, Assigned: isabel_rios)

Details

Attachments

(1 file)

Due to the latest changes on xcode and iOS version. This error has started to appear frequently when running the tests. The tests fail when trying to go to TabTray from BrowserTab, although the button is shown it is not available when the tests try to tap on it and so they fail. Since it is not possible to add a wait for that button in the ScreenGraph to wait to go to the TabTray once the button for that is available it would be needed to add that wait in the tests that are failing if possible. Examples of tests that have failed due to that so far: -testTabCountShowsOnlyNormalOrPrivateTabCount -testClosePrivateTabsOptionClosesPrivateTabs -testClosePrivateTabsOptionClosesPrivateTabsShortCutiPad -testSearchFieldClearedAfterVisingWebsite -testSearchTabs -testLandscapeNavigationWithTabSwitch -testPrivateClosedSiteDoesNotAppearOnRecentlyClos But this error could appear in any test that needs to go to TabTray.
Similarly, there is an error that cannot get from BrowserTab to PageOptionsMenu affecting the bookmarks tests: -testBookmarkingUI -testAccessBookmarksFromContextMenu In this case it is needed to wait for the page options menu button to be available before trying to open that menu.
-testTypingBadURL (failing on L#54 when trying to go to BrowserTabMenu from BrowserTab) The issue is similar, in the end the problem is that being in BrowserTab looks like the options there are not available although the buttons are there and ready to be used.
Attached file GitHub Pull Request
Assignee: nobody → irios.mozilla
Comment on attachment 9017605 [details] [review] GitHub Pull Request I hope that at least most of the routing issues from BrowserTab to TabTray are fixed now. If those issues are still seen I don't see other option but to go following each step in the test instead of using the graph...or if there is a better option I could try...
Attachment #9017605 - Flags: review?(npark)
Attachment #9017605 - Flags: review?(npark) → review+
Holding to land this PR since it adds many changes and tests started to pass again except for two or three that can be managed differently...
Landed on master: https://github.com/mozilla-mobile/firefox-ios/commit/920c18953810d7b79082a544f0f3a9b379912b2e Let's wait to uplift to v14.x until the issues do not appear on master
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: