commit 63ccd136c18a096a8b0a3aa49d6cf73405fe09ac
parent 8db860e6f9494a2ecb967bf7d86a05828f8ba1ff
Author: AndiAJ <andiaj@users.noreply.github.com>
Date: Thu, 2 Oct 2025 17:36:44 +0000
Bug 1822531 - Fix verifyAddressAutofillTest UI test r=aaronmt
The UI test was flaky when trying to set the text to the "Addresses" fields.
This was happening because we were dismissing the keyboard to have all fields in view.
By doing this in some cases it actually triggered a "go back" navigation existing the sub setting,
The keyboard dismissal isn't actually required, so I've removed it (most likely it was a leftover from when we ran the tests on the Pixel 2 which is a smaller device)
The UI test successfully passed 50x on Firebase ✅
All UI tests that use the fillAndSaveAddress function successfully passed 3x on Firebase ✅
Differential Revision: https://phabricator.services.mozilla.com/D267214
Diffstat:
1 file changed, 0 insertions(+), 3 deletions(-)
diff --git a/mobile/android/fenix/app/src/androidTest/java/org/mozilla/fenix/ui/robots/SettingsSubMenuAutofillRobot.kt b/mobile/android/fenix/app/src/androidTest/java/org/mozilla/fenix/ui/robots/SettingsSubMenuAutofillRobot.kt
@@ -363,9 +363,6 @@ class SettingsSubMenuAutofillRobot(private val composeTestRule: ComposeTestRule)
Log.i(TAG, "fillAndSaveAddress: Waiting for $waitingTime ms for \"Name\" text field to exist")
composeTestRule.waitUntilAtLeastOneExists(hasTestTag(EditAddressTestTag.NAME_FIELD), waitingTime)
Log.i(TAG, "fillAndSaveAddress: Waited for $waitingTime ms for \"Name\" text field to exist")
- Log.i(TAG, "fillAndSaveAddress: Trying to click device back button to dismiss keyboard using device back button")
- mDevice.pressBack()
- Log.i(TAG, "fillAndSaveAddress: Clicked device back button to dismiss keyboard using device back button")
Log.i(TAG, "fillAndSaveAddress: Trying to set \"Name\" to $name")
composeTestRule.nameTextInput().performTextInput(name)
Log.i(TAG, "fillAndSaveAddress: \"Name\" was set to $name")
