Description

Similar what we've done in the extension here, this PR implements same approach into mobile repository.
For more information please see thread here.

When an E2E test fails in CI and developer triggers a re-run, all tests in that chunk are executed again, not just the failed ones. This leads to:

• Wasted CI time: A chunk with 20 tests where only 1 failed will re-run all 20 tests
• Increased costs: Unnecessary compute resources consumed on re-runs
• Slower feedback loop: Developers wait longer to verify if a flaky test passes on retry
• Inefficient debugging: When investigating flaky tests, having to wait for unrelated tests adds friction

For example, with 20 parallel chunks each running ~15 tests, a single flaky test failure triggers a re-run of the entire chunk (~15 tests) instead of just the 1 failed test.

For solution; implement selective test re-runs that automatically detect when a job is being re-run and skip tests that already passed.

• First run (run_attempt = 1): Tests run normally, results are uploaded as artifacts
• Re-run (run_attempt > 1):
  • Download the previous run's test result artifacts
  • Parse XML results to extract passed test file paths
  • Run all tests in the chunk EXCEPT those that passed
  • Skip execution entirely if all tests in the chunk passed previously

Validation of PR:

Intentionally broke tests here: c8f029f

On attempt1 it failed but other tests passed: https://github.com/MetaMask/metamask-mobile/actions/runs/20751876785/attempts/1?pr=24263

On attempt2 it only run failed test and skipped already passed tests: https://github.com/MetaMask/metamask-mobile/actions/runs/20751876785/attempts/2?pr=24263

Logs from attempt 2:

Found 8 executed test files
Found 2 failed test files
Found 6 fully passed test files
Failed tests: e2e/specs/confirmations-redesigned/transactions/send-max-transfer.spec.ts, e2e/specs/confirmations-redesigned/transactions/send-max-transfer-retry-1.spec.ts
Previous run results: 6 passed, 2 failed
This chunk: 1 failed, 0 not executed

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.