Technical Test Plan — "Saved Carts" Feature Release (v3.4)

Project / release: Marketplace Web — Saved Carts, v3.4 Author: Priya Nair, QA Lead Date: 5 June 2026 Reviewers: D. Osei (Eng Lead), L. Mertens (Product) Status: Approved

---

1. Scope and objectives

This plan covers testing of the new Saved Carts feature, which lets signed-in shoppers save a cart and return to it later from any device. The objective is to confirm carts persist correctly across sessions and devices, that guest and signed-in behaviour is correct, and that the feature does not regress the existing checkout flow before the v3.4 release.

2. In scope / out of scope

In scope

• Saving, loading, and clearing a cart for signed-in users
• Cart sync across two devices for the same account
• Merge behaviour when a guest with an active cart signs in
• Regression of the existing checkout path

Out of scope

• The payment provider's own processing (covered by its SLA and sandbox)
• Native mobile apps (web only this release)

3. Test approach and levels

Level	Included?	Type(s)	Manual / Automated	Owner
Unit	Yes	Functional	Automated	Dev
Integration	Yes	Functional	Automated	Dev
System	Yes	Functional, Performance	Mixed	QA
End-to-end	Yes	Functional	Automated (Playwright)	QA
Security	Yes	Security	Manual	Security
UAT	Yes	Acceptance	Manual	Product

4. Test cases

ID	Scenario	Expected result	Priority
TC-01	Signed-in user adds 3 items, signs out, signs back in	All 3 items still in the saved cart	High
TC-02	Same account opens the cart on a second device	Cart contents match within 5 seconds	High
TC-03	Guest with 2 items signs in to an account that already has 1 saved item	Carts merge to 3 distinct items, no duplicates	High
TC-04	User clears the saved cart	Cart empties on all devices on next load	Medium
TC-05	Save attempt while the cart service is unreachable	Friendly error shown; local cart preserved	Medium

5. Test environments and data

• Environment: Staging, configured to mirror production (same DB engine and cart-service version).
• Browsers/devices: Chrome and Safari on desktop; Chrome on Android; Safari on iOS.
• Test data: Three seeded accounts (empty, single-item, full cart) plus a guest session. No production customer data is used; all accounts are synthetic.

6. Entry and exit criteria

Entry criteria

• v3.4 release candidate deployed to staging
• Seeded accounts and test data loaded
• Feature spec signed off by Product

Exit criteria

• All High-priority cases (TC-01 to TC-03) executed and passed
• No open Critical or High-severity defects
• Checkout regression suite green
• UAT sign-off received from L. Mertens (Product)

7. Risks and mitigations

Risk	Likelihood	Impact	Mitigation
Cross-device sync lag under load	Medium	High	Add a performance pass on TC-02 at 200 concurrent users
Guest-merge edge cases missed	Medium	High	Pair-test TC-03 with the developer who built the merge logic