End-to-end: new member journey from sign-up to cancellation
App: TrendKart, a practice fashion marketplace (Myntra-style). Login: Guest checkout works; members: arya@trendkart.test / Trendy@123 or register. REST API: tests call it as /api/... through the request fixture or page.request; GET /api lists every endpoint ↗.
Interview scenario
"Our highest-value flow is a new member who signs up, saves things, buys with a member coupon and later cancels. Automate it end to end: sign up in the UI, seed the wishlist through the API, move an item to the bag and add another in the UI, apply NEWUSER, pay to a saved address created through the API, then verify the order through the API and cancel it in the UI."
Acceptance criteria
- UI: create an account with a unique email (Create an account link, then Name, Mobile, Email, Password). API: GET /api/me returns that email.
- API: POST /api/wishlist for productId 106. UI: on the wishlist choose size S and Move to bag; open product 104, pick size M, add to bag; in the bag set its quantity to 2 and apply NEWUSER, asserting the coupon message.
- API: GET /api/bag totals must equal what the bag page shows (count 3, Total Amount). POST /api/addresses for a saved address.
- UI: PLACE ORDER, choose the saved address and Cash on delivery, CONFIRM ORDER and assert the confirmation. API: GET /api/orders has that order with status confirmed and the same total. UI: open the order from My Orders, Cancel order, and assert the status is cancelled; API agrees.
🔒 This lab is part of Pro
Pro unlocks the live editor, the scenario checks and the reference solutions in Playwright and Selenium Java for all 38 labs, plus every interview answer. One payment of ₹1,299, lifetime access. Already on a lower tier? Upgrade for the difference.