Test redeeming points for a statement credit

The flow under test

Three figures are in play and they have to agree with each other rather than merely be present.

• The rate - 0.6 cents per point, stated on the page rather than implied.
• The conversion - 5,000 points producing a $30.00 credit, which is exactly that rate applied.
• The deduction - a balance falling from 84,200 to 79,200.
• The pending state - the credit listed as pending rather than applied, because it has not reached a statement yet.

Asserting the rate alongside the resulting credit is what makes the conversion verifiable. A credit of $30.00 is only correct in the context of the rate the page is advertising.

The test file

The starting balance is captured in the first step, so the deduction asserted at the end is a movement rather than a value that might always have read that way.

---
mode: testing
url: https://my-testing-repo-main.vercel.app/amex-clone-app/rewards?reset=true
max_steps: 40
tags: [american-express, banking, rewards]
---

# Amrex 25.1: Membership rewards redemption

Catalog objective: redeem points for a statement credit.
Key assertion: points are deducted and the credit shows as pending.

## Verify the starting balance
Verify the page subtitle reads "84,200 points available" and "Rate" reads "0.6 cents per point".

## Set the redemption
Leave "Points to redeem" as "5000" and verify "Statement credit" reads "$30.00".

## Redeem
Click "Redeem" and verify a green banner titled "Redemption submitted" says 5,000 points were redeemed for a $30.00 statement credit.

## Verify the deduction and the pending credit
Verify "Points balance" now reads "79,200" and the "Statement credits" card lists "$30.00" from 5,000 points with a "Pending" badge.

The pending badge is asserted explicitly, since a redemption that immediately reports itself as applied misrepresents when the customer will actually see the money.

Step by step coverage

A balance, a conversion, the action, and the record.

The deduction and the credit are asserted in the same step, which is what proves one caused the other rather than both happening to be true.

Running it

kane-cli testmd run tests/american-express/rewards-redemption_test.md

Add a redemption larger than the balance, since refusing it is the behaviour that protects both sides.

Loyalty balances are worth reconciling against the service rather than the screen. Calling an API inside a flow covers that, and the Kane CLI introduction covers getting the first run going.