Test a multi-store cart with separate fees and slots

The flow under test

The failure mode in a multi-store cart is not that it breaks. It is that the two stores start sharing something they should not, and the interface looks entirely normal while it happens.

• Grouping - the panel reports two stores and names both, rather than merging the items into one list.
• Independent fees - GreenLeaf at $3.99 and BulkBarn at $5.49, two different numbers on the same page.
• Independent windows - an afternoon slot on one store and an evening slot on the other, each selected in its own card.

The final step is the strongest assertion in the file. Selecting a different window per store and then checking both remain selected in their own cards is what proves the selection handler is scoped to a store rather than to the page.

The test file

Each store card is referenced by its name, and the slot is referenced by the label a shopper reads. The test never needs to know that there are two structurally identical cards on the page.

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

# Instacrate 7.1: Multi-store cart

Catalog objective: add items from two stores and verify separate delivery slots.
Key assertion: each store cart has its own slot and fee.

## Add an item from the first store
Click "Add" on "Organic Strawberries, 1 lb" and verify the carts panel shows "GreenLeaf Market".

## Add an item from a second store
Click "Add" on "Coffee Beans, 2 lb" and verify the carts panel shows "Your carts (2 stores)" with both "GreenLeaf Market" and "BulkBarn Wholesale".

## Open checkout
Click "Go to checkout" and verify the checkout page shows "2 stores · each delivers separately".

## Confirm each store has its own fees
Verify the GreenLeaf Market card shows a service fee of "$3.99" and the BulkBarn Wholesale card shows a service fee of "$5.49".

## Confirm each store picks its own window
Click "Within 2 hours · 3:00pm - 5:00pm" in the GreenLeaf Market card, click "This evening · 6:00pm - 8:00pm" in the BulkBarn Wholesale card, and verify both options are selected in their own store cards.

Run the test with:

kane-cli testmd run tests/instacart/multi-store-cart_test.md

The run

Five passes. The fee comparison was the cheapest step at 24.9 seconds, since it asserts two values against a checkout page that is already open.

---
test: ../multi-store-cart_test.md
status: passed
started: 2026-09-15T10:27:01.603Z
duration_s: 185
session_id: 076d6b55-a2ab-4506-bb54-3403a893e9ea
---

# Instacrate 7.1: Multi-store cart - Result

## Add an item from the first store ✓ passed (32.4s)
md5: 450d503e242545989a75fd9902b8a431
Click "Add" on "Organic Strawberries, 1 lb" and verify the carts panel shows "GreenLeaf Market".

## Add an item from a second store ✓ passed (34.6s)
md5: 86101415600e9682d8e8e27fcd4f985e
Click "Add" on "Coffee Beans, 2 lb" and verify the carts panel shows "Your carts (2 stores)" with both "GreenLeaf Market" and "BulkBarn Wholesale".

## Open checkout ✓ passed (34.3s)
md5: 05fa0ba2ac5f998b9cf8fce0515b16c3
Click "Go to checkout" and verify the checkout page shows "2 stores · each delivers separately".

## Confirm each store has its own fees ✓ passed (24.9s)
md5: 83da1d4293dacf2d1d419240883b75a2
Verify the GreenLeaf Market card shows a service fee of "$3.99" and the BulkBarn Wholesale card shows a service fee of "$5.49".

## Confirm each store picks its own window ✓ passed (41.4s)
md5: f0a043d3f22d0a0d71be2c43d1b0166f
Click "Within 2 hours · 3:00pm - 5:00pm" in the GreenLeaf Market card, click "This evening · 6:00pm - 8:00pm" in the BulkBarn Wholesale card, and verify both options are selected in their own store cards.

Reading the evidence

The result is a test that proves two carts stayed independent, which is the whole promise of a multi-store basket. It reads clearly enough that an operations lead can confirm the fee figures are the right ones.

The same scoping question comes up in any interface that repeats a card or a row with its own controls. How assertions resolve on the live page explains the mechanism, and the test.md format covers keeping related flows in one place.