Test a transfer status timeline and its current step

The flow under test

A status timeline fails in a way that generates support contacts rather than errors: it renders every stage correctly and marks the wrong one as current.

• The transfer is the right one - identified by reference and recipient together.
• The amounts are consistent - sent, received, fee and an arrival estimate.
• All four stages render - from setup through to delivery.
• The current stage is correct - marked explicitly, not inferred from styling.

The fourth step is what makes this more than a static check. It advances the transfer and asserts the marker moved to the next stage, which proves the timeline reflects state rather than displaying a fixed position.

The test file

All four stage labels are asserted together in one instruction, then the current marker separately, so a timeline missing a stage and a timeline highlighting the wrong one are different failures.

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

# Wize 15.3: Transfer tracking

Catalog objective: open an in-flight transfer and check its status steps.
Key assertion: the timeline shows the current step accurately.

## Open the in-flight transfer
Click "Track" on the "TR-80114" row and verify the page title reads "Transfer TR-80114" with the subtitle "To Mira Shah".

## Verify the amounts
Verify "You sent" reads "$500.00", "They receive" reads "₹41,481.29", "Fee" reads "$2.86" and "Estimated arrival" reads "by Wednesday, 17 September".

## Verify the current step
Verify the timeline lists "You set up the transfer", "We received your money", "We paid out your money" and "Money delivered", with a badge reading "Current step: We received your money".

## Advance the transfer
Click "Simulate next step" and verify the badge now reads "Current step: We paid out your money".

The arrival estimate is checked alongside the amounts rather than on its own, since it is part of the same promise the customer is tracking against.

Step by step coverage

Three assertions about the current state, then one about a transition.

Separating the stage list from the current marker is the detail worth copying. A page that renders all four labels and highlights the wrong one satisfies a list-only assertion completely.

Running it

kane-cli testmd run tests/wise/transfer-tracking_test.md

Against a live environment, drive the advance through whatever mechanism the real system uses rather than a simulation control.

Status surfaces are where a cached page is most likely to mislead. Running a flow interactively is the fastest way to explore that, and Kane CLI as a QA agent covers building the surrounding suite.