test: remove timer if isE2E

[racitores]

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

Skips starting the background transactions polling timer when the app goes to background if running in E2E, by gating it behind isE2E and importing the flag.

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

• Selected E2E tags: SmokeCore
• Risk Level: low
• AI Confidence: 85%

click to see 🤖 AI reasoning details

The change modifies app/components/Nav/Main/index.js to skip running BackgroundTimer.runBackgroundTimer for updating incoming transactions when the app is in E2E test mode (isE2E). This is a test infrastructure optimization that:

1. Only affects E2E test runs: The isE2E flag is true only when process.env.IS_TEST === 'true' or process.env.METAMASK_ENVIRONMENT === 'e2e'
2. Does not change production behavior: The background timer for transaction updates still runs normally in production
3. Is a common pattern: The isE2E flag is already used in many places throughout the codebase (e.g., usePna25BottomSheet, useMultichainAccountsIntroModal, useRewardsIntroModal, e2eBridgePerps) for similar purposes
4. Simple conditional wrapper: The change just wraps existing code in an if (!isE2E) check

The Main component is a core navigation component that handles app state changes, notifications, and network switching. Running SmokeCore tests will verify that the core wallet functionality and navigation still work correctly with this change. Since the change is specifically designed to improve E2E test stability and doesn't modify any business logic, the risk is low.

View GitHub Actions results

[sonarqubecloud]

Quality Gate failed

Failed conditions
D Maintainability Rating on New Code (required ≥ A)

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE