Versions Compared

Old Version 44

changes.mady.by.user Capovilla, Evandro

Saved on

compared with

New Version 45

changes.mady.by.user Capovilla, Evandro

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Test Scenario

Steps

Screenshots

SCENARIO 1: The user makes a payment

  1. The user selects MB Way from the payment list.

  2. The user fills in the phone number field.

  3. The user is redirected to the "Waiting for Payment" screen.

  4. The user accepts the payment in the MB Way app.

  5. The user returns to the whitelabel app.

  6. The user is redirected to the order confirmation page.

https://www.figma.com/design/RtD0UFtwuwXx14lbLCAPlr/branch/OWwFfjThLHwiZkB2dvJKgv/9.-Checkout?node-id=40558-24217&t=OZuRKZNKCPJTSM5t-0

SCENARIO 2: The user makes a payment and closes the whitelabel app ( Delivery )

  1. The user selects MB Way from the payment list.

  2. The user fills in the phone number field.

  3. The user is redirected to the "Waiting for Payment" screen.

  4. The user closes the whitelabel app.

  5. The user accepts the payment in the MB Way app.

  6. The user returns to the whitelabel app.

  7. A tracking modal appears for the user to track the order.

https://www.figma.com/design/RtD0UFtwuwXx14lbLCAPlr/branch/OWwFfjThLHwiZkB2dvJKgv/9.-Checkout?node-id=42110-4286&t=OZuRKZNKCPJTSM5t-0

SCENARIO 3: The user makes a payment and closes the whitelabel app ( Pickup )

  1. The user selects MB Way from the payment list.

  2. The user fills in the phone number field.

  3. The user is redirected to the "Waiting for Payment" screen.

  4. The user closes the whitelabel app.

  5. The user accepts the payment in the MB Way app.

  6. The user returns to the whitelabel app.

https://www.figma.com/design/RtD0UFtwuwXx14lbLCAPlr/branch/OWwFfjThLHwiZkB2dvJKgv/9.-Checkout?node-id=42110-4287&t=OZuRKZNKCPJTSM5t-0

SCENARIO 4: The user makes a payment, closes the whitelabel app, doesn't pay in the MB Way app, opens the whitelabel app, the payment is still valid and user is redirect to waiting payment page.

  1. The user selects MB Way from the payment list.

  2. The user fills in the phone number field.

  3. The user is redirected to the "Waiting for Payment" screen.

  4. The user closes the whitelabel app.

  5. The user returns to the whitelabel app.

  6. The user is redirect to waiting payment page

https://www.figma.com/design/RtD0UFtwuwXx14lbLCAPlr/branch/OWwFfjThLHwiZkB2dvJKgv/9.-Checkout?node-id=42037-29391&t=G7781FC1ZSRNblsB-0

SCENARIO 6: The user enters an incorrect phone number

  1. The user selects MB Way from the payment list.

  2. The user fills in the phone number field with an incorrect number.

  3. An error modal appears.

https://www.figma.com/design/RtD0UFtwuwXx14lbLCAPlr/branch/OWwFfjThLHwiZkB2dvJKgv/9.-Checkout?node-id=42037-29246&t=OZuRKZNKCPJTSM5t-0

SCENARIO 7: The user makes a payment and the time limit expires

  1. The user selects MB Way from the payment list.

  2. The user fills in the phone number field.

  3. The user is redirected to the "Waiting for Payment" screen.

  4. The timer finishes, and an error modal appears.

https://www.figma.com/design/RtD0UFtwuwXx14lbLCAPlr/branch/OWwFfjThLHwiZkB2dvJKgv/9.-Checkout?node-id=42037-29247&t=OZuRKZNKCPJTSM5t-0

SCENARIO 8: The user makes a payment and cancels in the MB Way app

  1. The user selects MB Way from the payment list.

  2. The user fills in the phone number field.

  3. The user is redirected to the "Waiting for Payment" screen.

  4. The user cancels the payment in the MB Way app.

  5. An error modal appears.

https://www.figma.com/design/RtD0UFtwuwXx14lbLCAPlr/branch/OWwFfjThLHwiZkB2dvJKgv/9.-Checkout?node-id=42037-29247&t=OZuRKZNKCPJTSM5t-0

SCENARIO 9: Guest receives the email after placing the order

  1. The user selects MB Way from the payment list.

  2. The user fills in the phone number field.

  3. The user is redirected to the "Waiting for Payment" screen.

  4. The user accepts the payment in the MB Way app.

  5. The user returns to the white-label app.

  6. The user is redirected to the order confirmation page.

  7. The user receives an email informing them that the order has been placed.

image-20240119-170853.png

SCENARIO 10: The support tool user can see the order receipt

  1. The order is placed.

  2. The support user can see the order in the support tool.

  3. The support user selects the order.

  4. The support user can see the order details.

  5. The support user can see that the order is paid via the MB Way app.

SCENARIO 11: The DOP user can see the order receipt

  1. The order is placed.

  2. The user can see the order in the DOP.

  3. The user selects the order.

  4. The user can see the order details.

  5. The user can see that the order is paid via the MB Way app.

SCENARIO 12: The DMP user can see the order receipt

  1. The order is placed.

  2. The user can see the order in the DMP.

  3. The user selects the order.

  4. The user can see the order details.

  5. The user can see that the order is paid via the MB Way app.

SCENARIO 13: Make a refund in the support tool

  1. The order is placed.

  2. The support user can see the order in the support tool.

  3. The support user selects the order.

  4. The support user can see the order details.

  5. The support user can make a refund.

SCENARIO 14: Make a partial refund in the support tool

  1. The order is placed.

  2. The support user can see the order in the support tool.

  3. The support user selects the order.

  4. The support user can see the order details.

  5. The support user can make a partial refund.

SCENARIO 15: Make a refund in DMP

  1. The order is placed.

  2. The user can see the order in the DMP.

  3. The user selects the order.

  4. The user can see the order details.

  5. The user can make a refund.

SCENARIO 16: Autorefund

  1. The order is placed.

  2. The order is cancelled for any reason.

  3. The autorefund is triggered by the system.

  4. The support user can see the order in the support tool.

  5. The order is refunded

SCENARIO 17: Phone input error

  1. The user selects MB Way from the payment list.

  2. The user fills in the phone number field a wrong value.

  3. The user see a payment error modal

  4. The user continues in the payment page

Image Removed

  1. cannot click continue button.

Image Added

SCENARIO 18: Payment Refused

  1. The user selects MB Way from the payment list.

  2. The user fills in the phone number field.

  3. The user is redirected to the "Waiting for Payment" screen.

  4. The user refuse the payment in the MB Way app.

  5. The user see a payment refused modal

  6. The user is redirect to cart page

SCENARIO 19: Payment Refused by time expired

  1. The user selects MB Way from the payment list.

  2. The user fills in the phone number field a wrong value.

  3. The user is redirected to the "Waiting for Payment" screen.

  4. The user waits for time limit to end

  5. The user see a payment refused modal

  6. The user is redirect to cart page

SCENARIO 20: Insert a phone number without iso code country

  1. The user selects MB Way from the payment list.

  2. The user fills in the phone number field with only phonenumber (e.g., 983334571).

  3. The user is redirect to waiting payment page.

SCENARIO 21: Insert a phone number with iso code country

  1. The user selects MB Way from the payment list.

  2. The user fills in the phone number field with only phonenumber (e.g., 351 983334571).

  3. The user is redirect to waiting payment page.

...