Description

There is an existing detox issue where the tests would fail with the following error:

Error: Unable to update lock within the stale threshold
    at /Users/vagrant/git/node_modules/proper-lockfile/lib/lockfile.js:[REDACTED]09:2[REDACTED]
    at newFs.<computed> [as utimes] (/Users/vagrant/git/node_modules/proper-lockfile/lib/adapter.js:20:[REDACTED]3)
    at Timeout._onTimeout (/Users/vagrant/git/node_modules/proper-lockfile/lib/lockfile.js:[REDACTED]00:20)
    at listOnTimeout (node:internal/timers:58[REDACTED]:[REDACTED]7)
    at process.processTimers (node:internal/timers:5[REDACTED]9:7) {
  code: 'ECOMPROMISED'
}

The issue is stemming from Detox itself and was reported here. Unfortunately there is no fix available. One of the commenters suggested booting the simulator prior to running the test rather than letting Detox handle it during test execution.

The purpose of this PR is to add a bitrise step in the ios_e2e_test workflow that boots the simulator before executing the tests.

Related issues

Fixes: https://consensyssoftware.atlassian.net/browse/MMQA-411

Manual testing steps

1. Go to this page...

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.