Test a statement download producing a real file

The flow under test

The assertion that matters is the byte count, which is the only thing distinguishing a working download from a broken one.

• The statement is listed - the right month against the right account.
• The download reports - a notice naming the statement and a byte count.
• The file is not empty - a byte count greater than zero.
• The history agrees - the download recorded with the same byte count.

A zero byte PDF opens as a corrupt file rather than an error, and the customer discovers it when they forward it to an accountant. Asserting the size is what catches a generator that fails without throwing.

The test file

The statement is identified by month and account together, since an account with several statements makes either value alone ambiguous.

---
mode: testing
url: https://my-testing-repo-main.vercel.app/chase-clone-app?reset=true
max_steps: 50
tags: [chase, banking, documents]
---

# Chaise Bank 23.4: Statement download

Catalog objective: download last month's statement PDF.
Key assertion: the PDF downloads and is non-empty.

## Sign in
Type "priya.nair" into "Username", "Bank2026!" into "Password", click "Sign in", type "483921" into "One-time code", and click "Verify and sign in".

## Open the statements page
Go to https://my-testing-repo-main.vercel.app/chase-clone-app/statements and verify the available statements list includes "August 2026" for "Total Checking".

## Download it
Click "Download PDF" on the August 2026 Total Checking statement and verify a notice says the statement for August 2026 was downloaded with a byte count.

## Verify the file is non-empty
Verify the statement row now shows a byte count greater than zero, and the download history lists "August 2026 · Total Checking" with that same byte count.

The byte count is asserted in two places, on the row and in the download history, which catches a history record written independently of the actual file.

Step by step coverage

A login, a location, a download and a verification.

Comparing the two byte counts is the assertion worth copying. A history record that disagrees with the file it describes is a reconciliation problem for anyone auditing document delivery.

Running it

kane-cli testmd run tests/chase/statement-download_test.md

Add a variant for a month with no statement, since the empty state is what a customer meets most often and is least likely to be designed.

File handling is a common gap in browser test coverage. File handling in Kane CLI covers downloads and attachments, and the open evidence format covers what a run records about them.