Page Comparison

...

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
Analytics user	User responsible for checking the events on mParticle/Amplitude.

Whitelabel

Test Part 1:

In order to perform these scenarios, it will be necessary to manipulate the content of the Lokalise existing on the local environment according to the pre-conditions for each test case:

...

Scenario 1: [Split logic][Mapped errors][Title message] Validate the split logic on the title message when all the errors are mapped on the Lokalise
Scenario 2: [Split logic][Non-mapped errors][Title message] Validate the split logic on the title message when some errors are NOT mapped on the Lokalise
Scenario 3: [Split logic][Mapped errors][Message description] Validate the split logic on the message description when all the errors are mapped on the Lokalise
Scenario 4: [Split logic][Non-mapped errors][Message description] Validate the split logic on the message description when some errors are NOT mapped on the Lokalise
Scenario 5: [Split logic][Mapped errors][Modal button] Validate the split logic on the modal button when all the errors are mapped on the Lokalise
Scenario 6: [Split logic][Non-mapped errors][Modal button] Validate the split logic on the modal button when some errors are NOT mapped on the Lokalise

Test Part 2:

We will be able to use Paycomet’s instruction to simulate some of the mapped errors. In this case, we need to use the CVV field and enter the code informed by Paycomet. The codes are availabe on this document.

...

Analytics

Test Part 3:

...

Versions Compared

Old Version 6

New Version 7

Key

Whitelabel

Test Part 1:

Test Part 2:

Analytics

Test Part 3: