Consolidate unified-input Maestro tests into one file

[malmstein]

Task/Issue URL: https://app.asana.com/1/137249556945/project/488551667048375/task/1214927873722256?focus=true
Testing scenarios: https://app.asana.com/1/137249556945/project/488551667048375/task/1215056189493585?focus=true

Description

Lands the full unified-input Maestro suite under .maestro/unified_input_screen/. Replaces the six per-combination unified_input_with_favorites_*.yaml files from the seeders work with a single consolidated test, and adds six new top-level tests covering the From-Search / New-Tab scenarios from the Native Input Widget E2E backlog plus a Duck.ai chat → Search navigation test.

Every top-level test pins nativeInputToggle: "true", uses addFavorites: "example.com;duckduckgo.com;privacytest.com", and wraps each iteration in retry: maxRetries: 3. The Duck.ai-side tests pin inputWithAiToggle: "true" and sweep omnibarPosition ∈ {top, bottom, split} (three iterations each). unified_input_with_seeded_favorites keeps the AI on/off sweep (six iterations) because the assertion is AI-independent.

Layout under .maestro/unified_input_screen/:

unified_input_with_seeded_favorites.yaml      # 6 iters (positions × AI)
unified_input_open_chat_move_to_search.yaml   # 3 iters (positions, AI on)
unified_input_search_suggestions.yaml         # 3 iters
unified_input_ask_duckai_suggestion.yaml      # 3 iters
unified_input_duckai_model_reasoning.yaml     # 3 iters
unified_input_duckai_tool_pills.yaml          # 3 iters
unified_input_duckai_web_search_prompt.yaml   # 3 iters
shared/
  launch_and_skip_onboarding.yaml             # local skip helper (see below)
  assert_seeded_favorites_visible.yaml
  open_new_chat.yaml
  flow_search_suggestions.yaml
  flow_ask_duckai_suggestion.yaml
  flow_duckai_model_reasoning.yaml
  flow_duckai_tool_pills.yaml
  flow_duckai_web_search_prompt.yaml

Scenarios covered

Test	What it verifies
unified_input_with_seeded_favorites	Three seeded favorites visible on the NTP across all omnibar positions and AI states
unified_input_open_chat_move_to_search	Open Duck.ai chat, submit query, switch back to Search mode and run a regular search
unified_input_search_suggestions	Autocomplete suggestions appear when typing in Search mode; submitting dismisses the unified input and loads the SERP
unified_input_ask_duckai_suggestion	"Ask Duck.ai" autocomplete row opens Duck.ai with the typed query submitted
unified_input_duckai_model_reasoning	Model picker opens, switching model updates the chip; reasoning picker opens, picking a non-default effort persists on re-open
unified_input_duckai_tool_pills	Selecting Web Search / Create Image from the options menu places an active pill; tapping the pill removes the tool
unified_input_duckai_web_search_prompt	Web Search applies to the first prompt and clears for the follow-up — the tool is per-prompt, not sticky

Infrastructure notes

• shared/launch_and_skip_onboarding.yaml — robust local replacement for ../../shared/skip_all_onboarding.yaml. The upstream skip falls back to ../../shared/pre_onboarding.yaml whose asserted welcome copy has drifted from the new onboarding build, and the Skip Onboarding button bounds straddle the status bar height so tap-by-id is intercepted by the system bar. This helper waits for the button, taps by point at the bottom of its bounds, and waits for the unified input to settle.
• addFavorites values are URL-list strings (semicolon-separated hosts) — matches the landed AddFavoritesSeederPlugin semantics from Add Maestro test seeding for NativeInputWidget E2E tests #8418.
• All YAMLs target appId: com.duckduckgo.mobile.android (not .debug) to match the binary used in CI / Robin / Maestro Cloud.

CI wiring

.github/workflows/e2e-nightly-non-blockers-suite.yml adds a Unified Input Field step that runs the suite on Maestro Cloud, scoped via the unifiedInputTest tag, and reports failures to Asana.

Steps to test this PR

• Install: ./gradlew installPlayDebug
• Run the whole suite: maestro test .maestro/unified_input_screen --include-tags unifiedInputTest
• All seven top-level tests pass — 24 iterations total (six tests × three positions plus the seeded-favorites test's six AI-and-position combos)

UI changes

Before	After
N/A — test-only change	N/A — test-only change

[joshliebe]

Check the comments from Cursor, otherwise LGTM

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit d6b01c7. Configure here.}

[cursor]

Missing wait for T&C dialog causes test flakiness

Medium Severity

The T&C handling in open_new_chat.yaml uses assertVisible: optional: true + tapOn: optional: true without any extendedWaitUntil, unlike the other new flows in this PR (flow_ask_duckai_suggestion.yaml, flow_duckai_web_search_prompt.yaml) which correctly use runFlow: ../../shared/accept_duckai_agreement.yaml. That shared flow waits up to 10 seconds for the dialog to appear. Since every iteration launches with clearState: true, the T&C dialog will always appear on first Duck.ai use, but the inline optional check will race the WebView load — if it completes before the dialog renders, the dialog goes undismissed and blocks subsequent steps like tapOn: "Ask anything privately…".

 

^{Reviewed by Cursor Bugbot for commit d6b01c7. Configure here.}