Test delivery slot checkout with fees carried to confirmation

The checks that matter

Fees are the part of a slot flow that goes wrong, because they are calculated in one place, displayed in another and persisted in a third.

Repeating the fee assertion on the confirmation is what proves it persisted rather than merely rendered. A priority fee charged at checkout and absent from the order record is a reconciliation problem for whoever pays the driver.

The same flow as a test file

The slot is referenced by its full label, priority tier and time window together, because a slot flow that selects the right time at the wrong tier produces a plausible-looking order at the wrong price.

---
mode: testing
url: https://my-testing-repo-main.vercel.app/instacart-clone-app?reset=true
max_steps: 45
tags: [instacart, grocery, checkout]
---

# Instacrate 7.3: Delivery slot checkout

Catalog objective: choose a priority slot and complete checkout with a test card.
Key assertion: confirmation shows the chosen window and fees.

## Add an item and open checkout
Click "Add" on "Organic Strawberries, 1 lb", click "Go to checkout", and verify the checkout page shows "GreenLeaf Market".

## Choose the priority slot
Click "Priority - within 1 hour · 2:00pm - 3:00pm" and verify the store card shows a priority fee of "$4.99".

## Pay with the test card
Type "4242 4242 4242 4242" into the card number field, click "$5.00" for the tip, and verify the order total shows "$23.84".

## Place the order
Click "Place order" and verify the confirmation shows "Order placed" with an order number starting with "IC-".

## Confirm the window and fees carried through
Verify the confirmation shows a delivery window of "Priority - within 1 hour · 2:00pm - 3:00pm", a service fee of "$3.99" and a priority fee of "$4.99".

Run the test with:

kane-cli testmd run tests/instacart/delivery-slot-checkout_test.md

Run output

This run is dated 21 September and is materially faster than the 15 September runs elsewhere in this set. Four of its five steps completed in under a second each.

---
test: ../delivery-slot-checkout_test.md
status: passed
started: 2026-09-21T12:27:12.053Z
duration_s: 57
session_id: 62befbe6-8ff9-40e5-8d68-2fb4b8c13649
---

# Instacrate 7.3: Delivery slot checkout - Result

## Add an item and open checkout ✓ passed (3.25s)
md5: ad9800a8437ef29922ce8a763c6ed14e
Click "Add" on "Organic Strawberries, 1 lb", click "Go to checkout", and verify the checkout page shows "GreenLeaf Market".

## Choose the priority slot ✓ passed (0.79s)
md5: 7cbd2b236ebbbf0f72edea91e0a2611d
Click "Priority - within 1 hour · 2:00pm - 3:00pm" and verify the store card shows a priority fee of "$4.99".

## Pay with the test card ✓ passed (0.94s)
md5: 44e8c7714ebe8b19b84c7df8479f5bbe
Type "4242 4242 4242 4242" into the card number field, click "$5.00" for the tip, and verify the order total shows "$23.84".

## Place the order ✓ passed (0.8s)
md5: deaddda42da5310c9084a2574d2be2db
Click "Place order" and verify the confirmation shows "Order placed" with an order number starting with "IC-".

## Confirm the window and fees carried through ✓ passed (44.9s)
md5: 73115b003857ed556bb04bcaa6037ee5
Verify the confirmation shows a delivery window of "Priority - within 1 hour · 2:00pm - 3:00pm", a service fee of "$3.99" and a priority fee of "$4.99".

The final step still cost 44.9 seconds because it asserts three separate values on a freshly rendered confirmation page. The four steps before it act on pages that are already loaded and resolved, which is where the speed comes from.

Taking it further

What you have is a checkout test that follows a fee from selection through to the order record, in a file that runs in under a minute.

The run time difference between the two dates in this set is worth understanding if you are planning suite size. The Kane CLI speed work covers what changed, and running flows in CI covers budgeting a pipeline around it.