* For #26792 - Change active Firebase Test Lab emulator from x86 to ARM
Update startup-test kind.yml Jobs for ARM
Update ui-test kind.yml Jobs for ARM
Cleans up and renames Flank configurations for ARM
Updates ui-test.sh for ARM
* Fix BookmarksTest.kt and HomeScreenTest.kt
* Fix intent matcher for SettingsAboutTest
Adds a helper function for Play Store intent
* Fix SettingsSearchTest.kt
* ktlint fix TestHelper.kt and SettingsRobot.kt
* Let relbot update A-C on trunk
We already use relbot for this on fenix release branches and on all
branches for focus-android, so might as well avoid the duplication.
* Update mergify rules to auto-merge AC bumps from relbot on the main branch
Setups up a new daily cron task to run select UI tests on API 28 (we’ll call it legacy). We don’t necessarily want to invoke Flank twice (serial) with a different configuration (FTL APIs dont support API splitting per test-target) on event CI but we do want them running elsewhere (cron).
* Fixes#11427 - Rename master branch to main (Automation/TC)
* Fixes#11427 - Rename master branch to main (GitHub Workflows)
* Fixes#11427 - Rename master branch to main (GitHub Workflows)
* Fixes#11427 - Rename master branch to main (GitHub Issue Templates)
* Fixes#11427 - Rename master branch to main (Jenkins)
* Fixes#11427 - Rename master branch to main (README & Documentation)
* Fixes#11427 - Rename master branch to main (Jenkins)
* Fixes#11427 - Rename master branch to main (Random)
Speculative fix based on the Firebase logs which shows that on a second check
of R.id.tab_wrapper it is not found the screen.
It may be because after `advanceToHalfExpandedState` and before getting a
reference to it in `waitForTabTrayBehaviorToIdle` it was already animated off
the screen.
With this in mind I've added a null check for the view reference before trying
to register an idling resource on it's Behavior.
Also added and used a way to click at a specific location in a View, not just
in the default middle in the View.
It was observed from the Firebase videos that a "click" on the topBar actually
selected the private tabs section. This would leave us to believe that the
"click" was caught by that other View which was placed above the x,y middle of
the topBar.
* run-ui-test-nightly
* Run ui tests on nightly build
* set correct number of shard according to tests running
* fix typo
* removing testing file
Co-authored-by: isabel rios <isabelrios@MBP-de-isabel-2.home>
fix: flank_snapshot requires direct shard value
-1 shards -> 50 shards
fix: adjust flank-x86.yml shard value
try old results generator in flank-x86.yml
fix: legacy-junit-report -> legacy-junit-result
revert to modern reporting
