Using the Coffee cart app: https://coffee-cart.app/, I can think of test cases for when the user is viewing the cart page.
Zero Entries: Cart Page
-
If the user hasn’t selected a coffee, no coffee should display
-
When the user is viewing the cart page, they see a message notifying them that the cart is empty and that they can take action to change that.
One Entry - Cart page
- When a user adds one cup of coffee, they see the coffee they selected, how much the coffee costs, the number of coffee cups they’ve added, and the user has the option to add or remove the coffee that exists in the cart
- The user can add the same type of coffee from the cart page and the count updates
- The user can remove the same type of coffee from the cart page and the count updates
- The user can remove a specific type of coffee from the cart page
- Only the coffees selected should be visible
- The cart navigation displays the correct count of the selected number of coffees
- The payment total updates correctly
Many Entries: Cart page - The user selects ten different types of coffees
(I won’t repeat the test cases above related to the “One entry” - but the same applies for “Many Entries”)
- All ten cups of selected coffees display.
- The page displays the different types of coffee in rows that the user can plainly see
- The list of coffee types display in alphabetical order
