Test filing a claim and the payout it calculates

The checks that matter

The payout is the assertion that matters, because it is a subtraction the customer will check and dispute.

Asserting all three rather than the payout alone is what distinguishes a correct calculation from a coincidence. A deductible applied twice, or not at all, produces a number that still looks like money.

The flow as a test file

The recorder step asserts the state before and after, moving from ready to recorded, which proves the capture registered rather than the button merely responding.

---
mode: testing
url: https://my-testing-repo-main.vercel.app/lemonade-clone-app/quote?reset=true
max_steps: 60
tags: [lemonade, insurance, claims]
---

# Limonade 26.3: Claim filing video flow

Catalog objective: file a claim describing an incident.
Key assertion: the claim is submitted with a claim id.

## Get a policy in place
Type "Priya" into "Your name", click "Next", click "Next", click "See my price", click "Buy this policy", type "4242 4242 4242 4242" into "Card number", click "Activate my policy", and verify the policy shows an "Active" badge.

## Describe the incident
Go to https://my-testing-repo-main.vercel.app/lemonade-clone-app/claims, select "Theft" in "Type of claim", leave "Roughly what is it worth" as "850", type "My bike was taken from the building's bike store overnight." into "Tell us in your own words", and click "Next".

## Record the statement
Verify the recorder reads "Ready to record", click "Record statement", and verify it now reads "Statement recorded".

## Submit and verify the claim id
Click "Submit the claim" and verify a green card titled "Claim submitted" shows "Claim id" of "CLM-48120", "Type" of "Theft", "Claimed" of "$850.00", "Deductible" of "$500.00", "Expected payout" of "$350.00" and a "Submitted" badge.

The step ceiling is 60, the highest in this batch, because the flow buys a policy before it can file a claim against it.

Step by step coverage

A policy, an incident, a statement and the claim.

The claim id is what the customer quotes in every follow up, so it belongs in the assertion alongside the money.

Adding it to a suite

kane-cli testmd run tests/lemonade/claim-filing_test.md

Add a claim below the deductible, since the correct payout there is zero and a flow that pays out anyway is an expensive defect.

Setup-heavy flows like this are the strongest case for automation. Running flows asynchronously covers not waiting on them, and Kane CLI as a QA agent covers the surrounding suite.