Introduction

This document details how the Detailed payment error messages feature 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.
Amplitude	Data Analytics

Application

Description

POS

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

Kiosk

Call Center

Testing Subjects

Subject	Description

Subject	Description
Whitelabel	https://dev-bk-web.pt.rbi.tools/

User Role	Description
User	User will be placing successful orders on Whitelabel
Developer user	User responsible for enabling the FF on the Launch Darkly (LD) and setting which cards are accepted for each brand and country

Scenario	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	Mapped errors on Lokalise file according to the table below. Back-end FF on LD enabled.	Access the WL and go to the payment screen. Select credit card option. On CVV type the <CVV> and confirm. 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	Mapped and non-mapped errors on Lokalise file according to the table below. Back-end FF on LD enabled.	Access the WL and go to the payment screen. Select credit card option. On CVV type the <CVV> and confirm. 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	Mapped errors on Lokalise file according to the table below. Back-end FF on LD enabled.	Access the WL and go to the payment screen. Select credit card option. On CVV type the <CVV> and confirm. 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	Mapped and non-mapped errors on Lokalise file according to the table below. Back-end FF on LD enabled.	Access the WL and go to the payment screen. Select credit card option. On CVV type the <CVV> and confirm. 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.	Mapped and non-mapped errors on Lokalise file according to the table below. Back-end FF on LD enabled. mParticle/Amplitude access	Access the WL and go to the payment screen. Select credit card option. On CVV type the <CVV> and confirm. Check if the new event and its attributes are being sent properly to mParticle/Amplitude according to the table below.