[Bug]: SettingsPrivacyTest.launchLinksInPrivateToggleOffStateDoesntChangeTest fails locally on Pixel 2 (smaller screen devices?)

[mcomella]

Steps to reproduce

1. On the main branch, on a Pixel 2 (or perhaps any other device with a smaller screen such that the 3-dot menu requires 2 swipes to display the "Settings" menu item)...
2. Run SettingsPrivacyTest.launchLinksInPrivateToggleOffStateDoesntChangeTest

Expected behaviour

Test passes

Actual behaviour

Test fails with

androidx.test.uiautomator.UiObjectNotFoundException: UiSelector[SCROLLABLE=true]
at androidx.test.uiautomator.UiScrollable.scrollBackward(UiScrollable.java:496)
at androidx.test.uiautomator.UiScrollable.scrollToBeginning(UiScrollable.java:544)
at androidx.test.uiautomator.UiScrollable.scrollToBeginning(UiScrollable.java:563)
at androidx.test.uiautomator.UiScrollable.scrollIntoView(UiScrollable.java:265)
at androidx.test.uiautomator.UiScrollable.scrollTextIntoView(UiScrollable.java:336)
at org.mozilla.fenix.helpers.TestHelper.scrollToElementByText(TestHelper.kt:52)
at org.mozilla.fenix.ui.robots.SettingsRobot$Transition.openPrivateBrowsingSubMenu(SettingsRobot.kt:209)
at org.mozilla.fenix.ui.SettingsPrivacyTest.launchLinksInPrivateToggleOffStateDoesntChangeTest(SettingsPrivacyTest.kt:356)

I believe what is happening is the settings menu is not opened right before openPrivateBrowsingSubMenu is called https://searchfox.org/mozilla-mobile/rev/becaeeb6fe4268631ff8155be9f3662917ee1bb3/fenix/app/src/androidTest/java/org/mozilla/fenix/ui/SettingsPrivacyTest.kt#356 so openPrivateBrowsingSubMenu throws an assertion error because it doesn't see the text it's supposed to see. I think the reason the Settings menu isn't opened is because the 3-dot menu now requires a click and two swipes up to reach the bottom – perhaps the automated clicks are occurring too quickly.

Device name

Google Pixel 2

Android version

?

Firefox release type

Firefox Nightly

Firefox version

main branch: e2af42a

Device logs

No response

Additional information

No response

┆Issue is synchronized with this Jira Task