Description

Refactors E2E smoke tagging to better match feature ownership and test scope, and updates all downstream consumers (specs, workflows, Bitrise, analyzer/docs).

Main changes:

• Replaced SmokeTrade with:
  • SmokeSwap for tests/smoke/swap/*
  • SmokeStake for tests/smoke/stake/*
• Merged Card + Ramps under SmokeMoney:
  • Updated tests/smoke/card/* and tests/smoke/ramps/*
  • Removed deprecated SmokeCard and SmokeRamps
• Merged Seedless onboarding under SmokeAccounts:
  • Updated tests/smoke/seedless/*
  • Removed deprecated SmokeSeedlessOnboarding
• Added one extra Snap shard in smoke workflows:
  • iOS: snaps-ios-smoke 3 -> 4
  • Android: snaps-android-smoke 3 -> 4

Changelog

CHANGELOG entry: null

Related issues

Fixes:

Manual testing steps

Feature: Smoke tag taxonomy migration

  Scenario: run smoke workflows with new tags
    Given a branch with the updated smoke tags and workflow config
    When smoke workflows are triggered for iOS and Android
    Then tests in swap use SmokeSwap
    And tests in stake use SmokeStake
    And tests in card and ramps use SmokeMoney
    And tests in seedless use SmokeAccounts

  Scenario: verify deprecated tags are removed
    Given the updated repository
    When searching for SmokeTrade, SmokeCard, SmokeRamps, and SmokeSeedlessOnboarding
    Then no active smoke spec or smoke workflow references those tags

Screenshots/Recordings

Before

N/A (tag/workflow refactor)

After

N/A (tag/workflow refactor)

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.