test: adds diagnosis for launchArgs monitoring

[christopherferreira9]

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.

Performance checks (if applicable)

• I've tested on Android
  • Ideally on a mid-range device; emulator is acceptable
• I've tested with a power user scenario
  • Use these power-user SRPs to import wallets with many accounts and tokens
• I've instrumented key operations with Sentry traces for production performance metrics
  • See trace() for usage and addToken for an example

For performance guidelines and tooling, see the Performance Guide.

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

Medium Risk
Primarily affects E2E/test-only paths, but it adds new network proxy/diagnostic hooks in shim.js and posts extra data during app startup, which could impact test stability if misconfigured.

Overview
Adds an end-to-end diagnostics pipeline to make CI failures easier to debug. The app now records launch-argument/test config details on a shared globalThis testConfig, appends those details to fixture fetch URLs, and posts structured diagnostics (including remote feature flag update phases) back to the host mock server during E2E runs.

On the test runner side, MockServerE2E accepts /e2e-diagnostics, stores a bounded history, and includes recent diagnostics in “live request” failure errors; FixtureHelper.withFixtures captures rich failure artifacts (screenshots, view hierarchy, redacted metadata, mock-server/feature-flag request info) via a new tests/framework/E2EDiagnostics.ts, and the E2E GitHub Actions workflow now archives/uploads these diagnostics artifacts on failures.

^{Reviewed by Cursor Bugbot for commit 4c7a838. Bugbot is set up for automated code reviews on this repo. 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 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 c6acce5. Configure here.}

[github-actions]

🔍 Smart E2E Test Selection

⏭️ Smart E2E selection skipped - skip-smart-e2e-selection label found

All E2E tests pre-selected.

View GitHub Actions results

[sonarqubecloud]

Quality Gate failed

Failed conditions
50.0% Coverage on New Code (required ≥ 80%)
D Reliability 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