Test a coverage change and the premium that follows

The contract this flow keeps

A change preview makes three claims, and the one most often wrong is the delta rather than the new figure.

• The current state - $20,000.00 of cover at $17.90 a month, captured before anything changes.
• The new premium - $23.40 a month at $30,000.00 of cover.
• The delta - plus $5.50 a month, which has to be the difference between the two.
• The direction - a badge saying the premium goes up, so the change is not ambiguous.

Asserting the delta alongside both premiums is what catches a preview that computes the new figure correctly and the difference wrongly. The delta is the number the customer actually decides on.

The objective in plain English

The preview is asserted before the change is applied, because a cost shown only after the customer has committed is not a preview.

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

# Limonade 26.4: Coverage adjustment

Catalog objective: increase the personal property coverage and verify the premium change.
Key assertion: the new premium reflects the change.

## 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.

## Verify the current coverage
Go to https://my-testing-repo-main.vercel.app/lemonade-clone-app/coverage and verify the "Today" card shows "Personal property" of "$20,000.00" and "Monthly premium" of "$17.90".

## Raise the personal property cover
Select "$30,000.00" in "Personal property" and verify "New monthly premium" reads "$23.40", "Change" reads "+$5.50 a month" and a badge reads "Premium goes up".

## Apply the change
Click "Apply the change" and verify a green banner says the premium is now $23.40 a month, up $5.50, and the "Today" card shows "Personal property" of "$30,000.00" with "Monthly premium" of "$23.40".

The final step re-asserts the today card, so the change is proven to have persisted onto the policy rather than only appearing in a confirmation banner.

Assertion by assertion

A policy, a baseline, a preview and the applied change.

Asserting the policy card again at the end is the step that matters. A confirmation banner is produced by the action; the policy card is the record.

Putting it in CI

kane-cli testmd run tests/lemonade/coverage-adjustment_test.md

Add a downgrade, since a reduction should lower the premium and a direction badge that always says up is a plausible bug.

Mid-term changes touch billing as well as cover. Calling an API in the same run covers checking the billing side, and running flows in CI covers doing it on every release.