Test reorder from purchase history

Failure modes in this flow

A reorder test that only checks item names passes the most common reorder bug. Quantities are carried by different code than the line items and they fail independently.

• The source order is what you think it is - W-2208145, status Picked up, total $24.07.
• Every line came across - all three items present in the cart by name.
• Quantities came across - 2 for the milk and 3 for the eggs, not 1 and 1.
• The arithmetic follows - a subtotal of $19.12, which only holds if the quantities are right.

The subtotal assertion is a cheap cross-check on the quantities. If the counts silently reset, the subtotal moves, and the test fails on a number rather than on a count nobody looks at.

Writing the objective

The reorder action names the button as the shopper sees it, including its item count, so a button that offers the wrong number of items fails before the cart is even opened.

---
mode: testing
url: https://my-testing-repo-main.vercel.app/walmart-clone-app/orders?reset=true
max_steps: 40
tags: [walmart, reorder]
---

# Wallmark 4.4: Reorder from history

Catalog objective: reorder a past purchase in two clicks from order history.
Key assertion: the cart is prefilled with the previous items.

## Confirm the purchase history
Verify the history shows order "W-2208145" with status "Picked up" and a total of "$24.07".

## Reorder the past purchase
Click "Reorder (3 items)" on order "W-2208145" and verify the storefront cart shows "Whole Milk, 1 gal", "Honey Wheat Bread" and "Large Eggs, 12 ct".

## Confirm the quantities came across
Verify the cart shows a quantity of "2" for "Whole Milk, 1 gal" and "3" for "Large Eggs, 12 ct", with a subtotal of "$19.12".

The step ceiling is 40 rather than 45 here, matching the shorter flow. Run the test with:

kane-cli testmd run tests/walmart/reorder-from-history_test.md

Running it locally

Three passes in 120 seconds, the second quickest run in the storefront set. The reorder click itself cost 43.2 seconds because it navigates from order history into the storefront cart.

---
test: ../reorder-from-history_test.md
status: passed
started: 2026-09-15T10:02:45.161Z
duration_s: 120
session_id: 098b23f0-d159-4a41-9515-af2a757d3163
---

# Wallmark 4.4: Reorder from history - Result

## Confirm the purchase history ✓ passed (33.5s)
md5: 4895a60a27c738330268341fca61bfdd
Verify the history shows order "W-2208145" with status "Picked up" and a total of "$24.07".

## Reorder the past purchase ✓ passed (43.2s)
md5: 8be384e792655eade47ddcdca9993682
Click "Reorder (3 items)" on order "W-2208145" and verify the storefront cart shows "Whole Milk, 1 gal", "Honey Wheat Bread" and "Large Eggs, 12 ct".

## Confirm the quantities came across ✓ passed (39.4s)
md5: 5386fc3f239586cefb46e4eccb805fa0
Verify the cart shows a quantity of "2" for "Whole Milk, 1 gal" and "3" for "Large Eggs, 12 ct", with a subtotal of "$19.12".

Putting it in CI

The result is a short retention-path test that checks the thing reorder actually gets wrong. It runs in two minutes and reads clearly enough that a product owner can confirm the expectations are the right ones.

Order history and reorder are natural neighbours for a small post-purchase suite. The test.md format covers keeping several related files together, and building a suite from a PRD covers doing it against written requirements.