Quick answer: Test a tnova cart edit as two separate actions: removing the original box, then adding a reviewed replacement. Verify that only the intended box group changes and that its box quantity is preserved. Also test leaving the edit and restoring the selection: neither action automatically puts the removed box back in the cart. If a result is uncertain, inspect the original cart before another write.
This is a merchant acceptance test for the implemented cart-page workflow, extending the theme-integration checklist. tnova is preparing for public installation; use an authorized test environment with a valid configuration and purchasing checks. The public sample picker cannot perform these cart tests.
Build a cart that exposes an incorrect replacement
Use the exact verified theme version and full cart page you intend to offer. Keep the default market/currency and the supported shared fulfillment location. A passing cart-page test does not establish cart-drawer compatibility.
In a fictional six-item box with a maximum of two units per variant, create:
| Cart group | Selection per box | Box quantity |
|---|---|---|
| A: selection to edit | Berry × 2, Cocoa × 2, Lemon × 2 | 2 |
| B: selection to leave alone | Berry × 1, Cocoa × 2, Lemon × 2, Mint × 1 | 1 |
| Standalone item | One Berry item outside either box | Not a box |
Use eligible test variants; the names above are placeholders. This cart has 12 component units in A, six in B and one standalone unit. Record each group and the current price before editing. Screenshots of a test cart are useful when they show the component quantities, rather than only the parent title.
The repeated parent product and shared Berry variant make this a stronger test than a cart containing only one box. Shopify's Cart API documentation explains that multiple cart lines can share a variant ID. The practical check is that the intended instance changes while the others remain intact; no developer-console commands are required.
Verify removal before expecting a replacement
On group A, select Remove these boxes and edit. The supported flow reads the cart, removes that instance, and reads the same cart again before returning to the picker. It does not perform an instant swap.
After confirmed removal, the picker should explain that you are editing two boxes, that the original boxes were removed, and that nothing will be added automatically. Check the restored selection against your record. The edit preserves the original box quantity; the item count still describes the contents of each box.
For the normal path, change A's per-box selection to Berry × 1, Cocoa × 2, Lemon × 2 and Mint × 1. Review the current price and complete six-item selection, then submit the replacement once. Inspect the cart:
- The replacement has two boxes, giving component totals of Berry × 2, Cocoa × 4, Lemon × 4 and Mint × 2.
- The original A selection is gone.
- Group B and the standalone Berry item remain unchanged.
- No extra copy was added alongside the replacement.
Use the actual grouped components to assess the result. A cart item counter or total alone cannot establish which selection was replaced.
Distinguish cancelling the edit from restoring the selection
Run each case with a fresh recorded test cart, so an earlier removal does not confuse the next result.
| Action after confirmed removal | Meaning to verify |
|---|---|
| Cancel editing and return to cart | Returns to the cart; it does not undo the confirmed removal |
| Restore original selection | Restores choices in the picker; it does not add a box |
| Review the restored choices and submit | Attempts a replacement under current price, rules and eligibility |
These distinctions matter for customer instructions. “Cancel to put your old box back” would misdescribe the flow. Likewise, seeing the original choices in the picker is not proof that they are in the cart.
If the configuration version or candidates changed, review the current selection and any visible message. Saved choices can require revision under the new rules; restoration is not a promise that an older selection or price remains purchasable. Handle merchant configuration changes using the published-box update procedure, rather than changing a live configuration casually during this test.
Treat an interrupted edit as an observation task
In a controlled test environment, record what happens when the connection fails around removal or replacement. Note which action had started and the exact message. Recover the connection and inspect the cart in the original browser before repeating an action.
If removal cannot be confirmed, do not add a second box as a workaround. If removal succeeded but the replacement did not, the cart can legitimately contain neither selection. If adding is unconfirmed, use Check previous add where offered and View cart to investigate. The picker-and-cart troubleshooting guide explains these recovery controls.
Keep browser data intact while investigating. Switching browsers or clearing storage can lose the information needed to associate the operation with its original cart. Do not interpret a different empty cart as proof that the original was removed. If the result stays uncertain, capture the available operation reference, time, configuration version, selection and message for support, without sharing cart tokens or passwords.
This flow includes confirmation checks, but it is not a guarantee of an atomic replacement across every theme or third-party cart app. Record any other cart scripts involved and retest the exact integration after a relevant change.
Keep a short acceptance record
For each case, save the theme/cart mode, configuration version, original group and quantity, action, visible outcome and observed final groups. Mark uncertain outcomes as unresolved. The normal replacement, cancellation, selection restoration and interruption cases answer different questions; one successful edit does not cover all four.
Resolve unexpected duplicates, changed unrelated groups or misleading recovery messages before offering that cart flow. Once the supported path is verified, use the test-order audit for the separate checkout and order checks.
*Prepared with AI assistance and checked against tnova's storefront implementation and Shopify's current Cart API documentation. The cart is a fictional test design, not a claim that these cases passed on a merchant's store.*
See a gift box in action
Try the sample picker with fictional products. It creates no cart or order.
Try the box builder