test: add testIDs for send flow UI automation

[j0ntz]

CHANGELOG

Does this branch warrant an entry to the CHANGELOG?

• Yes
• No

Dependencies

none

Requirements

If you have made any visual changes to the GUI. Make sure you have:

• Tested on iOS device
• Tested on Android device
• Tested on small-screen device (iPod Touch)
• Tested on large-screen device (tablet)

Description

Test-infrastructure only. No behavior or visual changes.

Adds stable testID props so UI automation can drive the send flow by selector instead of brittle text or coordinate matching:

• AddressTile2: sendAddressEnter, sendAddressMyself, sendAddressScan, sendAddressPaste.
• SafeSlider: confirmSliderThumb on the draggable thumb (the id the shared maestro confirm-slider flow already expects).

These were added while verifying the TON duplicate-transaction fix (edge-currency-accountbased#1059); the send flow had no stable selectors. Snapshot files updated to reflect the new props. Related to Asana task.

---

Note

Low Risk
Test-only props and snapshot updates; no production logic or UI behavior changes.

Overview
Adds stable testID props for Maestro/UI automation on the send flow—no behavior or visual changes.

AddressTile2 exposes sendAddressEnter, sendAddressMyself, sendAddressScan, and sendAddressPaste on the empty-recipient action buttons. SafeSlider sets confirmSliderThumb on the draggable thumb (shared confirm-slider automation). Snapshot tests and CHANGELOG are updated accordingly.

^{Reviewed by Cursor Bugbot for commit 59d23d0. Bugbot is set up for automated code reviews on this repo. Configure here.}

[j0ntz]

Test evidence: TON send flow driven via these testIDs (duplicate-tx fix in accountbased #1059)

These send-flow testIDs (SafeSlider confirm slider, AddressTile2 "Myself" picker) were used to drive a real wallet-to-wallet TON send in the running app (My Toncoin to My Toncoin 2, 0.0064 TON) to verify the TON duplicate-transaction fix in edge-currency-accountbased#1059.

1. Send executed to terminal success:

2. Transaction list after confirmation:

The send made with the fix (4:52 PM) is a single confirmed "Sent Toncoin" row. The 4:09 PM "Pending + Sent" pair below it is a PRE-fix send: the bug permanently writes two rows per pre-fix send, so that history stays in the list. Only the 4:52 PM send ran the fixed code.

Decisive proof from the wallet's transactionList.json (send rows, newest first):

Send	Stored entries	Result
post-fix (4:52 PM)	ONE: confirmed txid kdnHDSsg9MfKUPK0khLfeCJXI5DTDudIoO07TFIVo+w= (base64)	single entry
pre-fix (4:09 PM)	TWO: unconfirmed c90f2225... (hex) + confirmed imY+FtIL... (base64)	duplicate
pre-fix (earlier)	TWO: unconfirmed 19fde00d... (hex) + confirmed Gf3gDR7O... (base64)	duplicate

Every pre-fix send forks into a hex unconfirmed row plus a base64 confirmed row that never reconcile. With accountbased#1059 applied, the send is a single base64 confirmed row: the pending reconciled into the confirmed entry, duplicate gone.