Files
98202512eb tests(mobile): stable tx-card ids for E2E + drift-proof flows (#8319)
* feat(mobile): add stable per-transaction testID to transaction cards

TxInfo now stamps every card it renders with testID="tx-card-<txId>"
(caller-supplied testID wins), and the four card types that did not
forward SafeListItemProps (StakingTxExit, StakingTxWithdraw, TxBridge,
TxLifiSwap) now spread them like the rest. This lets E2E flows target a
transaction by identity instead of list position, which breaks whenever
the shared test Safe's queue drifts.

* tests(mobile): target safe-shield tx by id instead of list position

The shared test Safe's queue gained four conflicting nonce-3
transactions that all render as identical "Contract interaction"
cards, so TAP_INDEX: 1 opened the wrong transaction. tap-tx-card now
supports TAP_ID (scroll-until-visible + tap on the tx-card-<txId>
testID) and the malicious contract-interaction flow uses it; the
TAP_TEXT/TAP_INDEX path is unchanged for existing callers.

* tests(mobile): make change-currency robust to backend list order

The supported-fiat-codes endpoint now returns extra crypto tickers at
the head of the list, pushing EUR/GBP below the fold and breaking the
viewport assertions. Scroll to known entries in list order
(USD, EUR, GBP) instead of asserting on the initial viewport.

* tests(mobile): address review findings — order-independent flows

- change-currency: use the currency search field instead of scroll order
  assumptions; dismiss the keyboard before tapping a row (first tap only
  closes the keyboard otherwise) and match full row labels so the search
  input's own text can't be tapped.
- batch-3-actions-benign/-warn: migrate from TAP_INDEX to TAP_ID.
- tap-tx-card: treat whitespace-only TAP_ID as unset.
- TxInfo: document why the default testID precedes the props spread.

---------

Co-authored-by: Hanzo Dev <[email protected]>
2026-07-29 16:18:42 +02:00

65 lines
2.0 KiB
YAML

appId: ${APP_ID}
tags:
- transactions
- pending
- safe-shield
---
# ===========================================
# SafeShield: Contract Interaction (Malicious approve)
# ===========================================
# Safe: 0x65e1Ff7e0901055B3bea7D8b3AF457a659714013 (Polygon)
# Expected widget: Risk detected (CRITICAL)
# - Malicious threat detected (CRITICAL) - only one label
# - Balance change: No balance change detected
# - Risk disclaimer required
- runFlow:
file: ../../../../utils/setup/app-start.yml
- tapOn:
id: 'e2eSafeShieldSafe'
- assertVisible:
id: 'pending-tx-list'
# Malicious approve at nonce 16 — targeted by txId so queue reordering can't break it
- runFlow:
file: ../../../../utils/components/pending-tx/tap-tx-card.yml
env:
TAP_ID: 'tx-card-multisig_0x65e1Ff7e0901055B3bea7D8b3AF457a659714013_0x228751aa0f0442baf8a670e3af8bbe93c22c7e9a0ad14527620f9a50b972f52c'
- assertVisible: 'Confirm transaction'
# ===========================================
# SafeShield Widget
# ===========================================
- runFlow:
file: ../../../../utils/assertions/verify-safe-shield-widget.yml
env:
WIDGET_HEADER: 'Risk detected'
LABEL_1: 'Malicious threat detected'
VERIFY_DISCLAIMER: 'true'
# ===========================================
# Balance Change Block
# ===========================================
- runFlow:
file: ../../../../utils/assertions/verify-balance-change.yml
env:
NO_CHANGE: 'true'
# ===========================================
# SafeShield Details Sheet
# ===========================================
- runFlow:
file: ../../../../utils/assertions/verify-safe-shield-sheet.yml
env:
TAP_TO_OPEN: 'Risk detected'
HEADER: 'RISK DETECTED'
LABEL_1: 'Malicious threat detected'
DESCRIPTION_1: '.*known malicious address.*'
DESCRIPTION_1_2: '.*recorded malicious activity.*'
# Verify back on Confirm transaction screen
- assertVisible: 'Confirm transaction'