test: add component view tests for EVM and ERC-1155 send flows

[davibroc]

Adds 5 new view tests covering previously untested send scenarios:

• EVM ETH happy path (Amount → Recipient → Review button enabled)
• Invalid address disables Review with error text
• Token contract address opens SendAlertModal; cancel closes it
• Amount exceeding balance shows Insufficient funds on Continue
• ERC-1155 Amount screen shows NFT name and Next button lifecycle

Description

Changelog

CHANGELOG entry:

Related issues

Fixes:

Manual testing steps

Feature: my feature name

  Scenario: user [verb for user action]
    Given [describe expected initial app state]

    When user [verb for user action]
    Then [describe expected outcome]

Screenshots/Recordings

Before

After

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
Low risk since changes are limited to component-view tests and test mocks, with no production logic modifications.

Overview
Adds new component-view coverage for EVM send flows, including ETH happy path navigation, invalid recipient validation, insufficient-funds gating, and the token-contract recipient warning modal (with modal CANCEL_BUTTON/ACKNOWLEDGE_BUTTON test IDs).

Extends the component-view Engine mock to include AssetsContractController.getTokenStandardAndDetails, enabling tests to simulate token contract address detection and reset mock behavior between cases.

^{Written by Cursor Bugbot for commit b4acf8f. 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.

[cursor]

Cursor Bugbot has reviewed your changes and found 2 potential issues.

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

[github-actions]

🔍 Smart E2E Test Selection

• Selected E2E tags: None (no tests recommended)
• Selected Performance tags: None (no tests recommended)
• Risk Level: low
• AI Confidence: 97%

click to see 🤖 AI reasoning details

E2E Test Selection:
All three changed files are purely test/unit test infrastructure changes with zero production app code modifications:

1. tests/component-view/mocks.ts (CRITICAL path): Adds AssetsContractController.getTokenStandardAndDetails mock to the Engine mock used by component-view unit tests. This is a test infrastructure addition that enables new unit tests to run without errors. No production code is affected.

2. app/components/Views/confirmations/components/send/send-alert-modal/send-alert-modal.testIds.ts (new file): Defines test ID constants (CANCEL_BUTTON, ACKNOWLEDGE_BUTTON) for the send alert modal. This file is only imported in the unit test file (send.view.test.tsx) and not referenced in any E2E tests.

3. app/components/Views/confirmations/components/send/send.view.test.tsx: Adds new unit tests for EVM send flows (ETH happy path, invalid address validation, token contract address alert modal, insufficient funds, ERC-1155 NFT send). These are Jest/component-view unit tests, not Detox E2E tests.

No production app code was changed. No E2E test files were modified. The send-alert-modal.testIds.ts file is not referenced by any E2E test. The mock change in mocks.ts only affects component-view unit tests. There is no risk to any E2E test flows, and no performance-sensitive code was touched.

Performance Test Selection:
No production app code was changed. All modifications are limited to unit test files and test infrastructure (mocks, test IDs). There is no impact on UI rendering, state management, data loading, or any performance-sensitive code paths.

View GitHub Actions results

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud

[racitores]

LGTM