[Test Cases] Detailed payment error messages
- Hellen Rodrigues Magalhaes
Owned by Hellen Rodrigues Magalhaes
- 1 Whitelabel
- 1.1 Scenario 1: [Split logic][Mapped errors][Title message] Validate the different levels of error messages on the title message when all the errors are mapped on the Lokalise file
- 1.2 Scenario 2: [Split logic][Non-mapped errors][Title message] Validate the different levels of error messages on the title message when some errors are NOT mapped on the Lokalise file
- 1.3 Scenario 3: [Split logic][Mapped errors][Message description] Validate the different levels of error messages on the message description when all the errors are mapped on the Lokalise file
- 1.4 Scenario 4: [Split logic][Non-mapped errors][Message description] Validate the different levels of error messages on the message description when some errors are NOT mapped on the Lokalise file
- 1.5 Scenario 5: [Split logic][Mapped errors][Modal cta] Validate the different levels of error messages on the modal cta when all the errors are mapped on the Lokalise file
- 1.6 Scenario 6: [Split logic][Non-mapped errors][Modal cta] Validate the different levels of error messages on the modal cta when some errors are NOT mapped on the Lokalise
- 1.7 Scenario 7: [Mapped errors] Validate title error, modal description and modal cta according to the mapped errors on the Lokalise
- 1.8 Scenario 8: [Regression testing] Validate if the layout and responsive were kept on the existing error modal
- 1.9 Scenario 9: [Regression testing] Validate if the cta on the modal redirects the user to the cart page and the order is not placed
- 1.10 Scenario 10: [Mapped errors] Validate the modal using a different language according to the translation available on the Lokalise
- 1.11 Scenario 11: [Mapped errors] Validate the modal using a different language when the content is not available on the Lokalise
- 2 Analytics
- 2.1 Scenario 12: [Analytics] Validate if the attributes were added to the existing modal appearance event
- 2.2 Scenario 13: [Analytics] Validate if an attribute was removed on the existing modal appearance and if an attribute is being sent as "null”
- 2.3 Scenario 14: [Analytics] Validate if the new custom event “Error” is being triggered when the modal is displayed
- 2.4 Scenario 15: [Analytics] Validate analytics when the user set a different language from the default
- 2.5 Scenario 16: [Analytics] Validate the modal using a different language according to the translation available on the Lokalise
Whitelabel
Scenario 1: [Split logic][Mapped errors][Title message] Validate the different levels of error messages on the title message when all the errors are mapped on the Lokalise file
Feature: Detailed payment error messages feature
Background: Whitelabel Homepage
Given I have accessed Whitelabel's Home Page
Scenario Outline: As an user I should see the correct title message when all the errors are mapped on the Lokalise
Given I have all the errors mapped on the Lokalise
|error.payment.title |error.payment.2.title |error.payment.2.100.title |error.payment.2.100.001.title |
|Translation for the error error.payment.title |Translation for the error 2 Title |Translation for the error 2.100 Title |Translation for the error 2.100.001 Title|
|Translation for the error error.payment.title |Translation for the error 2 Title |Translation for the error 2.100 Title |Translation for the error 2.100.001 Title|
|Translation for the error error.payment.title |Translation for the error 2 Title |Translation for the error 2.100 Title |Translation for the error 2.100.001 Title|
And I simulate the error <simulate_error>
When I attempt to place a new order
Then I should be see the modal with the <title_message>
Examples:
|simulate_error |title_message |
|2.100.001 |Translation for the error 2.100.001 Title|
|2.100 |Translation for the error 2.100 Title |
|2 |Translation for the error 2 Title |
Scenario 2: [Split logic][Non-mapped errors][Title message] Validate the different levels of error messages on the title message when some errors are NOT mapped on the Lokalise file
Feature: Detailed payment error messages feature
Background: Whitelabel Homepage
Given I have accessed Whitelabel's Home Page
Scenario Outline: As an user I should see the correct title message when some errors are NOT mapped on the Lokalise
Given I do not have all the errors mapped on the Lokalise
|error.payment.title |error.payment.2.title |error.payment.2.100.title |error.payment.2.100.001.title |
|Translation for the error error.payment.title |Translation for the error 2 Title |Translation for the error 2.100 Title |null |
|Translation for the error error.payment.title |Translation for the error 2 Title |null |null |
|Translation for the error error.payment.title |null |null |null |
|Translation for the error error.payment.title |Translation for the error 2 Title |null |Translation for the error 2.100.001 Title|
|Translation for the error error.payment.title |null |null |Translation for the error 2.100.001 Title|
|Translation for the error error.payment.title |null |Translation for the error 2.100 Title |Translation for the error 2.100.001 Title|
And I simulate the error <simulate_error>
When I attempt to place a new order
Then I should be see the modal with the <title_message>
Examples:
|simulate_error |title_message |
|2.100.001 |Translation for the error 2.100 Title |
|2.100.001 |Translation for the error 2 Title |
|2.100.001 |Translation for the error error.payment.title|
|2.100 |Translation for the error 2 Title |
|2.100 |Translation for the error error.payment.title|
|2 |Translation for the error error.payment.title|
Scenario 3: [Split logic][Mapped errors][Message description] Validate the different levels of error messages on the message description when all the errors are mapped on the Lokalise file
Feature: Detailed payment error messages feature
Background: Whitelabel Homepage
Given I have accessed Whitelabel's Home Page
Scenario Outline: As an user I should see the correct message description when all the errors are mapped on the Lokalise
Given I have all the errors mapped on the Lokalise
|error.payment.default |error.payment.2 |error.payment.2.100 |error.payment.2.100.001 |
|Translation for the error error.payment.default |Translation for the error 2 |Translation for the error 2.100 |Translation for the error 2.100.001 |
|Translation for the error error.payment.default |Translation for the error 2 |Translation for the error 2.100 |Translation for the error 2.100.001 |
|Translation for the error error.payment.default |Translation for the error 2 |Translation for the error 2.100 |Translation for the error 2.100.001 |
And I simulate the error <simulate_error>
When I attempt to place a new order
Then I should be see the modal with the <message_description>
Examples:
|simulate_error |message_description |
|2.100.001 |Translation for the error 2.100.001|
|2.100 |Translation for the error 2.100 |
|2 |Translation for the error 2 |
Scenario 4: [Split logic][Non-mapped errors][Message description] Validate the different levels of error messages on the message description when some errors are NOT mapped on the Lokalise file
Scenario 5: [Split logic][Mapped errors][Modal cta] Validate the different levels of error messages on the modal cta when all the errors are mapped on the Lokalise file
Scenario 6: [Split logic][Non-mapped errors][Modal cta] Validate the different levels of error messages on the modal cta when some errors are NOT mapped on the Lokalise
Scenario 7: [Mapped errors] Validate title error, modal description and modal cta according to the mapped errors on the Lokalise
Scenario 8: [Regression testing] Validate if the layout and responsive were kept on the existing error modal
Scenario 9: [Regression testing] Validate if the cta on the modal redirects the user to the cart page and the order is not placed
Scenario 10: [Mapped errors] Validate the modal using a different language according to the translation available on the Lokalise
Scenario 11: [Mapped errors] Validate the modal using a different language when the content is not available on the Lokalise
Analytics
Scenario 12: [Analytics] Validate if the attributes were added to the existing modal appearance event
Scenario 13: [Analytics] Validate if an attribute was removed on the existing modal appearance and if an attribute is being sent as "null”
Scenario 14: [Analytics] Validate if the new custom event “Error” is being triggered when the modal is displayed
Scenario 15: [Analytics] Validate analytics when the user set a different language from the default
Scenario 16: [Analytics] Validate the modal using a different language according to the translation available on the Lokalise