Test adding a recipient and using them in a transfer

The contract this flow keeps

A saved recipient is only saved if it appears in the place that matters, and the two are handled by different code.

• The starting count - one saved recipient, so the addition is demonstrably new.
• The details are accepted - name, receiving currency, bank name and a full IBAN.
• The save is confirmed - a banner naming the recipient and the currency they can receive.
• The count increments and the recipient is selectable - two saved recipients, and the new one offered in a transfer set to their currency.

The final step is the one that separates this from a form test. It navigates to the send flow, switches the target currency and checks the new recipient is offered there, which is where a currency mismatch in the saved record would surface.

The objective in plain English

The account number is a full IBAN rather than a short value, because length and format validation is a large part of what this form is for.

---
mode: testing
url: https://my-testing-repo-main.vercel.app/wise-clone-app/recipients?reset=true
max_steps: 45
tags: [wise, payments, recipients]
---

# Wize 15.2: Add recipient

Catalog objective: add a bank recipient with account details.
Key assertion: the recipient is saved and selectable in a transfer.

## Open the recipient form
Verify "Saved recipients (1)" lists "Mira Shah", then click "Add recipient".

## Fill in the details
Type "Tom Alvarez" into "Full name", select "EUR" in "They receive", type "Banque Lumiere" into "Bank name", and type "FR7630006000011234567890189" into "Account number".

## Save
Click "Save recipient" and verify a green banner titled "Recipient saved" says "Tom Alvarez" can now receive EUR.

## Verify the recipient is selectable in a transfer
Verify the list now reads "Saved recipients (2)", then go to https://my-testing-repo-main.vercel.app/wise-clone-app/send, select "EUR" in "To currency", and verify "Tom Alvarez" is offered in the recipient dropdown.

Setting the target currency to EUR before checking the dropdown is deliberate. A recipient saved with the wrong currency is invisible at exactly the moment someone tries to pay them.

Assertion by assertion

The four steps take the recipient from a form to a usable option.

Asserting the count at the start and again at the end is a cheap way to prove one recipient was added, rather than zero or two.

Putting it in CI

kane-cli testmd run tests/wise/add-recipient_test.md

Add a second file covering a malformed account number, since rejecting bad input matters as much here as accepting good input.

Validation variants are the most mechanical thing to generate and the most tedious to write by hand. Generating validation cases covers that, and exact string assertions covers pinning each rejection message.