Description

This PR adapts the FixtureHelper (withFixtures) to work properly with appium and playwright.

Main changes:

• launchApp utility inside withFixtures now sends launchArgs so that FixtureServer and other resources can properly be used
• MockServer is completely tool agnostic
• App interaction is now segregated in specific handlers for adb and xcrun with an abstract CommandHandler
  • These are also exposed via test callback so that individual tests can interact with the device to clear app data, uninstall, install and so on
• Android amulator name is now automatically derived from its friendly name. Eg: PIXEL_XL_API_34 is not translated in the proper serial as emulator-5554
• FixtureServer now waits for an initial request to avoid early test start
• Tests now only start once Metro has finished loading. This prevents early fast fails where metro would take longer to load than the test would start.
  1. FixtureServer now counts completed GET /state.json requests.
  2. Before launching the app in Appium mode, withFixtures creates a waiter with fixtureServer.waitForNextStateRequest().
  3. Then PlaywrightUtilities.launchApp(...) launches the app with the fixture/mock/command server launch args.
  4. The app loads JS from Metro, runs the E2E bootstrap, and requests /state.json.
  5. When that request finishes, FixtureServer resolves the waiter.
  6. Only then does withFixtures continue to dismiss dev screens and run the actual test body.
• Appium server log level has been bumped to INFO to avoid clutter
• A boilerplate test using withFixtures has been added to be used as a guide for debugging
• Implemented different conditions to run tests locally on emulator:
  • buildPath is not provided - Framework checks for installed app, deletes app data and launches the app. Throws if the app is not installed.
  • buildPath is provided - App is uninstalled and installed back. Throws if the artifact does not exist.

Introduction of test shims:

This PR also adds a Playwright-only Node shim so FixtureBuilder can load in Playwright without changing app runtime behavior.
We need this shim mechanism because some app dependencies patch CommonJS packages to call native modules such as @metamask/native-utils. Those calls are valid in the mobile app, but Playwright loads the same dependency graph in Node where React Native/Nitro native modules are unavailable.

Changelog

CHANGELOG entry:

Related issues

Fixes:

• https://consensyssoftware.atlassian.net/browse/MMQA-1784
• https://consensyssoftware.atlassian.net/browse/MMQA-1742

Manual testing steps

N/A

Screenshots/Recordings

Before

N/A

After

N/A

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.