Test splitting a bill and the request it creates

The contract this flow keeps

The amount chosen is deliberately awkward, which is what makes this test worth having.

• The transaction - $42.15, an odd number that does not divide evenly.
• The split count - two people including the user, stated explicitly rather than implied.
• Each share - $21.07, which is the rounded half.
• The record - a badge on the transaction row stating it was split two ways at that amount.

Half of $42.15 is $21.075, so the interface has to round. Asserting $21.07 pins the rounding decision, and a change to that behaviour becomes a visible failure rather than a cent that appears or disappears unnoticed.

The objective in plain English

The split count is asserted as text including the user, because a split that excludes the person paying produces a plausible number for the wrong number of people.

---
mode: testing
url: https://my-testing-repo-main.vercel.app/revolut-clone-app/split?reset=true
max_steps: 40
tags: [revolut, fintech, p2p]
---

# Revolat 19.3: Split bill

Catalog objective: split a transaction with a contact.
Key assertion: a request is created for half the amount.

## Open the split panel
Click the split button on the "Metro Grocer" transaction and verify a panel titled "Split Metro Grocer · $42.15" appears.

## Choose one contact
Tick "Tom Alvarez" and verify "Split between" reads "2 people (including you)".

## Verify the share is half
Verify "Each pays" reads "$21.07".

## Request the money
Click "Request money" and verify a green banner titled "Split requested" says "$21.07" was requested from "Tom Alvarez" for Metro Grocer, split 2 ways, and the transaction row now shows a badge reading "Split 2 ways · $21.07 each".

The final step asserts both the request confirmation and the badge on the original transaction, which are separate records of the same action.

Assertion by assertion

A panel, a selection, the arithmetic, and the request.

Leaving the transaction marked as split is what prevents the same bill being split twice, which is the practical failure this record guards against.

Putting it in CI

kane-cli testmd run tests/revolut/split-bill_test.md

Add a three way split of the same amount, since dividing by three forces a rounding decision the two way case can avoid.

Rounding behaviour tends to change without anyone intending it to. Checking the UI before a pull request is where that belongs, and generating the variants covers producing the three and four way cases.