Versions Compared

Old Version 1

changes.mady.by.user Hellen Rodrigues Magalhaes

Saved on

compared with

New Version 2

changes.mady.by.user Hellen Rodrigues Magalhaes

Saved on

Key

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

...

This document details how the MB Way Detailed payment error messagesfeature should be tested

...

Test Scope

...

Application

Description

Whitelabel

Whitelabel’s is where guests finish placing their orders, either it’s on mobile or the web.

Launch Darkly

Feature management platform that allows development teams to control and manage feature flags to release software updates safely and continuously.

Lokalise

Translation management platform that helps teams streamline the localization process for their software and content.

Admin app

Tool used by Support area to solve the customers’s request and complaints.

DOP

Tool used by Franchisee to management restaurants.

Amplitude

Data Analytics

Out of Scope

Application

Description

POS

 

Won’t be tested as this application won’t be changed by this feature's development

Kiosk

Call Center

...

Traceability Matrix / Test Status

24

BK

PT

User kills the WL app and does not accept / time expires the payment on MB Way app

25

BK

PT

User kills the WL app and open it again meanwhile the time is not expired

26

BK

PT

User kills the WL app and open it again meanwhile the time is not expired - Place the order

27

BK

PT

Check refund process via Admin Tools

28

BK

PT

Check partial refund process via Admin Tools

29

PLK

ES

Check refund process via DMP

30

BK

PT

Check demand translation - Lokalise

31

BK

PT

Check if the "Payment is processing" splash screen is NOT displayed in any flow of MB Way

32

BK

PT

Check if the MB Way option is not available when the FF is disabled

33

BK

PT

Check the MB Way option filter by storeID on the LD

Scenario

Brand

Country

Test scenario

Test Execution Date

Test Status

1

BK

PT

Check if the MB Way new payment method is available on the dropdown

2

BK

PT

Check the MB Way icon

3

BK

PT

Check if submit form elements are displayed when the MB way method is selected

4

BK

PT

Check if submit form elements are NOT displayed when a different method than MB way is selected

5

BK

PT

Check submit form elements L&F

6

BK

PT

Check phone number imput validation

7

BK

PT

Check Continue button enable/disable

8

BK

PT

Check if the "Waiting payment" screen is displayed

9

BK

PT

Check the "Waiting payment" screen L&F

10

BK

PT

Check the count down animation

11

BK

PT

Check the confirmation order

12

BK

PT

Check new payment on Homeria

13

PLK

ES

Check new payment on DMP

14

BK

PT

Check new payment on DOP

15

BK

PT

Check new payment on Admin app tools

16

BK

PT

Unexisting phone number in MB Way

17

BK

PT

User refuses the payment on MB Way app

18

BK

PT

User does not accept / time expires

19

BK

PT

User just closes the WL app (keeping in background) and refuses the payment on MB Way app

20

BK

PT

User just closes the WL app (keeping in background) and does not accept / time expires the payment on MB Way app

21

BK

PT

User just closes the WL app (keeping in background) and open it again meanwhile the time is not expired

22

BK

PT

User just closes the WL app (keeping in background) and open it again meanwhile the time is not expired - Place the order

23

BK

PT

User kills the WL app and refuses the payment on MB Way app

Scenario Title

Pre- condition

How to execute(step-by-step)

1

[Mapped errors][Message Description] - Check if the custom description is displayed on the error modal

  1. Mapped errors on Lokalise file according to the table below.

  2. Back-end FF on LD enabled.

  1. Access the WL and go to the payment screen.

  2. Select credit card option.

  3. On CVV type the <CVV> and confirm.

  4. Check if the <Expected Message Description> is displayed on the error modal.

Scenario

Scenario Title

Pre- condition

How to execute(step-by-step)

2

[Non-Mapped errors][Message Description] - Check if the message description is displayed on the error modal

  1. Mapped and non-mapped errors on Lokalise file according to the table below.

  2. Back-end FF on LD enabled.

  1. Access the WL and go to the payment screen.

  2. Select credit card option.

  3. On CVV type the <CVV> and confirm.

  4. Check if the <Expected Message Description> is displayed on the error modal.

Scenario

Scenario Title

Pre- condition

How to execute(step-by-step)

3

[Mapped errors][Message Title] - Check if the message title is displayed on the error modal

  1. Mapped errors on Lokalise file according to the table below.

  2. Back-end FF on LD enabled.

  1. Access the WL and go to the payment screen.

  2. Select credit card option.

  3. On CVV type the <CVV> and confirm.

  4. Check if the <Expected Message Description> is displayed on the error modal.

Scenario

Scenario Title

Pre- condition

How to execute(step-by-step)

4

[Non-Mapped errors][Message Title] - Check if the message title is displayed on the error modal

  1. Mapped and non-mapped errors on Lokalise file according to the table below.

  2. Back-end FF on LD enabled.

  1. Access the WL and go to the payment screen.

  2. Select credit card option.

  3. On CVV type the <CVV> and confirm.

  4. Check if the <Expected Message Description> is displayed on the error modal.

Scenario

Scenario Title

Pre- condition

How to execute(step-by-step)

5

Analytics - Check if the new event and its attributes are being sent properly to mParticle/Amplitude according to the table below.

  1. Mapped and non-mapped errors on Lokalise file according to the table below.

  2. Back-end FF on LD enabled.

  3. mParticle/Amplitude access

  1. Access the WL and go to the payment screen.

  2. Select credit card option.

  3. On CVV type the <CVV> and confirm.

  4. Check if the new event and its attributes are being sent properly to mParticle/Amplitude according to the table below.