2057412 - Bug 2057412 - [efficiency] Add custom-tab launch capability + convert verifyCustomTabMenuItemsTest

Status: RESOLVED FIXED

(Firefox for Android :: UI Tests, task)

Description

[Jackie Johnson]

Custom tabs run in their own activity (CustomTabActivity), launched by an intent rather than an in-app
nav path. Adds that as a reusable harness capability:

• CustomTabsPage.launchCustomTab(url, customMenuItem): fires createCustomTabIntent at IntentReceiverActivity
  (FLAG_ACTIVITY_NEW_TASK), waits for the custom-tab toolbar, sets page state. No NavigationRegistry edge --
  custom tabs are launch-reached (this removes the previous illegal empty-steps edge). Plus openMainMenu().
• CustomTabsSelectors: device-level (UIAutomator) locators so they resolve across the activity switch --
  redesigned-toolbar menu button ("More options"), close button ("Return to previous app"), and main-menu items.
• PageContext gains on.customTabs.

Converts CustomTabsTest.verifyCustomTabMenuItemsTest (TestRail 249644). Green, non-flaky.
Unlocks the rest of the custom-tab family + the custom-tab connection variants (reuse the trust-panel verifier).

Why: Adds the custom-tab launch capability (custom tabs are intent-launched, not in-app nav-reachable), unlocking the whole custom-tab family.

Context: part of the ui/efficiency UI-test modernization. This adds framework capability/enablement (page objects, selectors, navigation edges, or BasePage primitives) required to convert legacy ui/ smoke tests onto ui/efficiency. Tracked separately from strict conversion so conversion effort can be measured over time. Epic MTE-5504.

TestRail: 249644

Comment 1

[Jackie Johnson]

Attachment: Bug 2057412 - [efficiency] Add custom-tab launch capability + convert verifyCustomTabMenuItemsTest r=aaronmt,isabel_rios

Custom tabs run in their own activity (CustomTabActivity), launched by an intent rather than an in-app
nav path. Adds that as a reusable harness capability:

• CustomTabsPage.launchCustomTab(url, customMenuItem): fires createCustomTabIntent at IntentReceiverActivity
  (FLAG_ACTIVITY_NEW_TASK), waits for the custom-tab toolbar, sets page state. No NavigationRegistry edge --
  custom tabs are launch-reached (this removes the previous illegal empty-steps edge). Plus openMainMenu().
• CustomTabsSelectors: device-level (UIAutomator) locators so they resolve across the activity switch --
  redesigned-toolbar menu button ("More options"), close button ("Return to previous app"), and main-menu items.
• PageContext gains on.customTabs.

Converts CustomTabsTest.verifyCustomTabMenuItemsTest (TestRail 249644). Green, non-flaky.
Unlocks the rest of the custom-tab family + the custom-tab connection variants (reuse the trust-panel verifier).

Comment 2

[Pulsebot]

Pushed by [e-mail]:
https://github.com/mozilla-firefox/firefox/commit/f2caae15afd5
https://hg.mozilla.org/integration/autoland/rev/88b299e4a39c
[efficiency] Add custom-tab launch capability + convert verifyCustomTabMenuItemsTest r=aaronmt,isabel_rios

Comment 3

[Serban Stanca [:SerbanS]]

https://hg.mozilla.org/mozilla-central/rev/88b299e4a39c