Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 18
Next »
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
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 |
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 |
: [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
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 some errors are NOT mapped on the Lokalise
Given I do not 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 |null |
|Translation for the error error.payment.default |Translation for the error 2 |null |null |
|Translation for the error error.payment.default |null |null |null |
|Translation for the error error.payment.default |Translation for the error 2 |null |Translation for the error 2.100.001|
|Translation for the error error.payment.default |null |null |Translation for the error 2.100.001|
|Translation for the error error.payment.default |null |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 |
|2.100.001 |Translation for the error 2 |
|2.100.001 |Translation for the error error.payment.default|
|2.100 |Translation for the error 2 |
|2.100 |Translation for the error error.payment.default|
|2 |Translation for the error error.payment.default|
Scenario 5: [Split logic][Mapped errors][Modal ] Validate the different levels of error messages on the modal cta 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 modal cta when all the error are mapped on the Lokalise
Given I have all the errors mapped on the Lokalise
|error.payment.cta |error.payment.2.cta |error.payment.2.100.cta |error.payment.2.100.001.cta |
|Translation for the error error.payment.cta |Translation for the error 2 cta |Translation for the error 2.100 cta |Translation for the error 2.100.001 cta|
|Translation for the error error.payment.cta |Translation for the error 2 cta |Translation for the error 2.100 cta |Translation for the error 2.100.001 cta|
|Translation for the error error.payment.cta |Translation for the error 2 cta |Translation for the error 2.100 cta |Translation for the error 2.100.001 cta|
And I simulate the error <simulate_error>
When I attempt to place a new order
Then I should be see the modal with the <modal_cta>
Examples:
|simulate_error |modal_cta |
|2.100.001 |Translation for the error 2.100.001 cta|
|2.100 |Translation for the error 2.100 cta |
|2 |Translation for the error 2 cta |
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
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 modal cta when some errors are NOT mapped on the Lokalise
Given I do not have all the errors mapped on the Lokalise
|error.payment.cta |error.payment.2.cta |error.payment.2.100.cta |error.payment.2.100.001.cta |
|Translation for the error error.payment.cta |Translation for the error 2 cta |Translation for the error 2.100 cta |null |
|Translation for the error error.payment.cta |Translation for the error 2 cta |null |null |
|Translation for the error error.payment.cta |null |null |null |
|Translation for the error error.payment.cta |Translation for the error 2 cta |null |Translation for the error 2.100.001 cta|
|Translation for the error error.payment.cta |null |null |Translation for the error 2.100.001 cta|
|Translation for the error error.payment.cta |null |Translation for the error 2.100 cta |Translation for the error 2.100.001 cta|
And I simulate the error <simulate_error>
When I attempt to place a new order
Then I should be see the modal with the <modal_cta>
Examples:
|simulate_error |title_message |
|2.100.001 |Translation for the error 2.100 cta |
|2.100.001 |Translation for the error 2 cta |
|2.100.001 |Translation for the error error.payment.cta|
|2.100 |Translation for the error 2 cta |
|2.100 |Translation for the error error.payment.cta|
|2 |Translation for the error error.payment.cta|
: [Mapped errors] Validate title error, modal description and modal cta according to the mapped errors on the Lokalise
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 error, modal description and modal cta according to the mapped errors on the Lokalise
Given I have all the errors mapped on the Lokalise
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>, the <message_description> and the <modal_cta>
Examples:
|simulate_error |title_message |message_description |modal_cta |
|2.100 |Card type invalid |Your card is not enabled to allow this payment at the moment. Please, contact your bank or try another payment method. |Pay another way |
|2.002 |Something went wrong |We had a problem processing this payment. Please try another payment method. |Pay another way |
|2.003 |Something went wrong |We had a problem processing this payment with this payment method. Please contact your bank support or try another payment method.|Pay another way |
|2.100 |Card type invalid |Your card is not enabled to allow this payment at the moment. Please, contact your bank or try another payment method. |Go back |
|2.100.001 |Validation error |The payment transaction was declined. Please check the Card information, number, CVV, expire date and try again. |Check the information|
Scenario 8: [Regression testing] Validate if the layout and responsive were kept on the existing error modal
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 that the correct layout and responsive were kept on the existing error modal
Given I have all the errors mapped on the Lokalise
And I simulate the error <simulate_error> on the platform <platform_browser>
When I attempt to place a new order
Then I should be see the layout and responsive being kept on the existing error modal
Examples:
|simulate_error |platform |
|2.100 |Chrome desktop|
|2.002 |Safari desktop|
|2.003 |Android app |
|2.100 |iPhone app |
Scenario 9: [Regression testing] Validate if the cta on the modal redirects the user to the cart page and the order is not placed
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 cta on the modal redirects the user to the cart page and the order is not placed
Given I have all the errors mapped on the Lokalise
And I simulate the error <simulate_error>
When I click on the modal error cta
Then I should be redirect to the cart page
And I should not see my order being placed
Examples:
|simulate_error |
|2.100 |
|2.002 |
|2.003 |
|2.100 |
Analytics
Scenario 10: [Analytics] Validate if the attributes were added to the existing modal appearance event
Feature: Detailed payment error messages feature
Background: Whitelabel Homepage
Given I have accessed Whitelabel's Home Page
Scenario Outline: As analytics user I should see the attributes added on the existing modal appearance event
Given I have all the errors mapped on the Lokalise
And I simulate the error <simulate_error>
And I attempt to place a new order
When the modal error is displayed
Then I should see the attributes added on the existing Modal Appearance event to the Amplitude: custom_event_type: others, ModalHeader <modal_header>, ModalMessage <modal_message> and Source Page: /cart/payment
Examples:
|simulate_error |modal_header |modal_message |
|2.100 |Card type invalid |Your card is not enabled to allow this payment at the moment. Please, contact your bank or try another payment method. |
|2.100.001 |Validation error |The payment transaction was declined. Please check the card name, card number, CVV, expire date and try again. |
|2.102.003 |Order limit exceeded |You have exceeded the number of attempts to place an order. Please try again later. |
Scenario 11: [Analytics]
Feature: Detailed payment error messages feature
Background: Whitelabel Homepage
Given I have accessed Whitelabel's Home Page
Scenario Outline: As analytics user I should see the attributes removed on the existing modal appearance event
Given I have all the errors mapped on the Lokalise
And I simulate the error <simulate_error>
And I attempt to place a new order
When the modal error is displayed
Then I should see the attribute removed on the existing Modal Appearance event to the Amplitude: Message
Then I should see the attribute as null on the existing Modal Appearance event to the Amplitude: MessageErrorMessage
Examples:
|simulate_error |
|2.100 |
|2.100.001 |
|2.102.003 |
Scenario 12: [Analytics]
Feature: Detailed payment error messages feature
Background: Whitelabel Homepage
Given I have accessed Whitelabel's Home Page
Scenario Outline: As analytics user I should see new custom event when the error modal is displayed
Given I have all the errors mapped on the Lokalise
And I simulate the error <simulate_error>
And I attempt to place a new order
When the modal error is displayed
Then I should see new custom event when the error modal is displayed to the Amplitude: event_name: Error, custom_event_type: others, Error Code <simulate_error> , Name <name>, Source Page: /cart/payment, Response Title <modal_header>, Response Description <modal_message>
Examples:
|simulate_error |name |modal_header |modal_message |
|2.100 | |Card type invalid |Your card is not enabled to allow this payment at the moment. Please, contact your bank or try another payment method. |
|2.002 | |Something went wrong |We had a problem processing this payment. Please try another payment method. |
Add Comment