Description

Adds checkStability and elemDescription options to the Gestures.waitAndTap calls inside the date, time, and date-time picker helpers in the TestSnaps page object. Stability checks prevent taps from firing on an element while it is still animating, and the descriptions surface clearer messages when a tap fails. No production code is affected.

Changelog

CHANGELOG entry: null

Related issues

Fixes: MMQA-1900

Manual testing steps

Feature: TestSnaps date/time picker E2E helpers

  Scenario: e2e suite drives the date-time picker via TestSnaps page object
    Given the test-snaps dapp is loaded on a device

    When the suite invokes selectDateInDateTimePicker / selectDateInDatePicker / selectTimeInTimePicker
    Then each tap waits for element stability before firing
    And failures report a human-readable element description

Screenshots/Recordings

Before

N/A — test-only change.

After

Coverage is provided by CI. All four snap Android smoke shards (which exercise the affected TestSnaps helpers) passed on this branch:

• snaps-android-smoke (1) — pass
• snaps-android-smoke (2) — pass
• snaps-android-smoke (3) — pass
• snaps-android-smoke (4) — pass

See checks on this PR for the run: https://github.com/MetaMask/metamask-mobile/pull/31085/checks

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.