test: add system tests tags

[pnarayanaswamy]

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

Low Risk
Low risk: changes are confined to Playwright test tagging/configuration and documentation, primarily affecting which tests are selected by --grep and CI scripts.

Overview
Introduces test-type tags @Performance and @System (in tests/tags.performance.js) and updates performance specs to include these tags in test.describe() names so Playwright configs can filter suites via grep.

Adds new package.json scripts to run system tests on local Android emulators and iOS simulators using tests/playwright.system-emulator.config.ts, and updates MM Connect and other performance/system specs to be grouped under the new tagging convention. Documentation in tests/performance/README.md is expanded to explain the new tag types, conventions, and examples.

^{Reviewed by Cursor Bugbot for commit 28088c1. 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.

[github-actions]

🔍 Smart E2E Test Selection

• Selected E2E tags: None (no tests recommended)
• Selected Performance tags: @PerformanceLaunch, @PerformanceLogin, @PerformanceOnboarding, @PerformanceAccountList, @PerformanceSwaps, @PerformanceAssetLoading, @PerformancePredict, @PerformancePreps
• Risk Level: low
• AI Confidence: 95%

click to see 🤖 AI reasoning details

E2E Test Selection:
All 38 changed files are exclusively within the performance test infrastructure (tests/performance/ directory, tests/playwright*.config.ts, tests/tags.performance.js, and package.json scripts). No app source code was modified.

Key changes:

1. tests/tags.performance.js: Added two new test-type tags @Performance and @System to complement existing area tags. These are runner-agnostic tags that control which Playwright config picks up a test.
2. tests/playwright.config.ts: Added grep: /@Performance/ to filter only performance-tagged tests.
3. tests/playwright.system.config.ts: Added grep: /@System/ to filter only system-tagged tests.
4. tests/playwright.system-emulator.config.ts: New config file for running system tests on local Android emulators and iOS simulators (instead of BrowserStack).
5. package.json: Added 4 new npm scripts for emulator/simulator system test execution.
6. All 30+ performance spec files: Updated to import and embed the new Performance and/or System tags in their test.describe() names — purely structural/tagging changes with no test logic modifications.

Since no Detox-based E2E app code was changed, no Detox E2E test tags are needed. The changes are confined to the Playwright-based performance test framework which is a completely separate test infrastructure from Detox.

Performance Test Selection:
All performance test spec files were modified to add the new @performance and @System tags to their test.describe() names. The new grep filters in playwright.config.ts (@performance) and playwright.system.config.ts (@System) mean tests will only be picked up if they have the correct tags. Running all performance test tags validates that: (1) the new tagging system correctly routes tests to the right config, (2) no tests were accidentally excluded by the new grep filters, and (3) the new emulator config (playwright.system-emulator.config.ts) works correctly. All area tags should be exercised to confirm the structural changes didn't break any test suite.

View GitHub Actions results

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud