test: add smoke swap trending tokens e2e coverage

[bfullam]

Description

Adds minimal SmokeTrade E2E coverage for Bridge Swap Trending Tokens zero-state behavior as a follow-up to the feature PR to keep implementation and test review separated.

Scope is intentionally narrow:

• Verifies zero-state trending section visibility and filter interaction flow.
• Verifies row navigation behavior from trending list.
• Uses existing smoke framework/page-object patterns.

Changelog

CHANGELOG entry: null

Related issues

Fixes: Follow-up coverage for #26620 (SWAPS-4038)

Manual testing steps

Feature: Swap trending tokens smoke coverage

  Scenario: user validates bridge zero-state trending interactions
    Given the app is running with swap trending tokens enabled
    And the user is on the Swap screen in Bridge zero state

    When the user opens and applies trending filters
    Then the trending list reflects the selected filters

    When the user taps a trending token row
    Then the user is navigated to that token's asset details

Screenshots/Recordings

Before

N/A (test-only follow-up PR)

After

N/A (test-only follow-up PR)

Pre-merge author checklist

• I've followed MetaMask Contributor Docs and MetaMask Mobile Coding Standards.
• I've completed the PR template to the best of my ability
• I've included tests if applicable
• I've documented my code using JSDoc format if applicable
• I've applied the right labels on the PR (see labeling guidelines). Not required for external contributors.

Pre-merge reviewer checklist

• I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
• I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.

---

Note

Low Risk
Test-only additions; primary risk is potential flakiness due to new Detox selectors, scrolling, and network mocking for trending tokens/feature flags.

Overview
Adds SmokeTrade E2E coverage for Swap Trending Tokens (Bridge zero-state), including a new SwapTrendingTokensView page object for interacting with the trending section, filters, bottom sheets, and token rows.

Introduces a new smoke spec that enables the swapsTrendingTokens remote flag, mocks the /v3/tokens/trending proxy responses (all networks vs Base-only), verifies filter behavior and default sort text, confirms tapping a row opens token details, and asserts the trending section hides once a swap amount is entered.

^{Written by Cursor Bugbot for commit 7e90d12. This will update automatically on new commits. Configure here.}

[github-actions]

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

[github-actions]

🔍 Smart E2E Test Selection

⏭️ Smart E2E selection skipped - base branch is not main (base: swaps-4038-trending-tokens)

All E2E tests pre-selected.

View GitHub Actions results

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[github-actions]

⚠️ E2E Fixture Validation — Structural changes detected

Category	Count
New keys	60
Missing keys	0
Type mismatches	0
Value mismatches	7 (informational)

The committed fixture schema is out of date. To update, comment:

@metamaskbot update-mobile-fixture

View full details | Download diff report

[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.}

[cursor]

High-priority feature flag mock silently shadows bridge-mocks setup

Medium Severity

setupSwapsTrendingTokensMock registers a regex-based feature flag mock at priority 1001, which intercepts all feature flag requests before the exact-URL mocks set up by testSpecificMock (from bridge-mocks.ts) at default priority. This means the bridgeConfigV2.chainRanking override from testSpecificMock is silently discarded — the response only contains default flags plus swapsTrendingTokens: true. The bridge UI depends on chainRanking for network pill ordering and availability. The test still passes because defaults include "Base", but the testSpecificMock feature flag setup is effectively dead code, and the test isn't running under the correct bridge configuration.

Additional Locations (1)

• tests/smoke/swap/swap-trending-tokens.spec.ts#L155-L161