Introduction
This document details how the Detailed payment error messages feature should be tested
Test Scope
In 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 |
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 |
Quality Objective
Ensure that all Acceptance Criteria has been met.
Ensure that all Test Cases has been executed and have passed.
Ensure that all bugs found has been fixed and retested before the release.
Test Methodology
Exploratory Testing
Functional Testing
Testing Tools
Testing Tools
Platform | Version | Description |
|---|---|---|
macOS | 15.0 |
|
Google Chrome | 126.0 |
|
Android Device | 14.0 |
|
iOS Device | 18.0 |
|
Insomnia | 9.3.0 | For backend tests |
Testing Subjects
Subject | Description |
|---|
Subject | Description |
|---|---|
Whitelabel |
Test Deliverables
Test Plan (this document)
Test Cases
Bug Tasks
Test Management
Test Actors
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 |
Key | CVV | Paycomet | Description | Modal Title | Modal Message | Modal CTA | Screen | |
|---|---|---|---|---|---|---|---|---|
Severity: 2 - NORMAL - Normal User Errors. | ||||||||
| 130 | Original operation not found. Could not refund | Operation not allowed for the credit card type | “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” |  | |
| Represents errors generated when a transaction is suspected of being fraudulent. | “Something went wrong" | “We had a problem processing this payment. Please try another payment method.” | "Pay another way” |  | |||
| Represents errors generated by internal fraud detection mechanisms within the system. | “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” |  | |||
| Represents errors that occur during the validation of transaction data, such as missing mandatory fields, incorrectly formatted data, and other validation failures. | “Validation error” | “The payment transaction was declined. Please check the card name, card number, CVV, expire date and try again.” | "Review Informations” |  | |||
| Represents an error related to credit/debit card transactions. | “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” |  | |||
| 111 | CVC2 block incorrect | The payment transaction was rejected because the user informed an invalid card CVV. | “Validation error" | “The payment transaction was declined. Please check the card name, card number, CVV, expire date and try again.” | "Review Informations” | | |
| Represents errors that arise during the payment processing phase, such as failures in communicating with the payment gateway, billing errors, and other issues that may occur while processing a payment. | “Something went wrong" | “We were unable to process this payment due to internal errors. Please try again later.” | "Go back” |  | |||
| 115 | Card issuer could not validate card owner | The payment transaction was rejected because card issuer could not validate card owner's identity. | “Identity error" | “Sorry, we were unable to verify the cardholder's identity. Please authorize payment and try again.” | "Go back” |  | |
| 1367 | When the same card has several payments in "flight" at the time that one is finalized, the rest are denied with this code. This restriction is for security. | Represents an error when In-Flight offline payments are rejected. An example of occurrence is when the same card has several payments in "flight" at the time and one is finalized, the rest might be denied. | “Something went wrong” | “Sorry, we are unable to process this payment. Please use another payment method.” | "Go back” |  | |
| Represents errors generated when a transaction is rejected as restricted by PSP or issuer. | “Something went wrong” | “Sorry, we are unable to process this payment. Please use another payment method." | "Go back” |  | |||
| 102 | Operation not allowed for the credit card type | Operation is not allowed for this card type. | “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” |  | |
| 1192 | Country (customer IP address) not allowed | Represents an error when the user's IP address is not from an allowed country. Ex.: Iberia payments only allowed from Spain and Portugal. | “Location Invalid" | “Sorry, we had a problem related to your location and this store. Please choose a nearest store and try again.” | "Choose another Store” |  | |
| 1202 | Number of failed attempts (last 30 minutes) from the same ip address exceeded | Represents an error when the number of failed attempts from the same user has been exceeded. | “Order limit exceeded" | “You have exceeded the number of attempts to place an order. Please try again later.” | "Go back” |  | |
Severity: 4 - ABNORMAL | ||||||||
| General, unspecified payment error. | “Failed Payment” | “Something went wrong with this payment. Please try again later” | "Go back” |  | |||
| Represents errors related to security and authentication within the payment system. Impact: All the payment transactions are failing. Solution: Investigate security related settings, like secrets. | “Failed Payment” | “Something went wrong with this payment. Please try again later” | "Go back” |  | |||
| Represents errors arising from system configuration issues. Impact: All the payment transactions are failing. Solution: Review the configuration for the specific service and PSP. | “Failed Payment” | “Something went wrong with this payment. Please try again later” | "Go back” | | |||
| Represents errors related to internal connection problems, such as failures in communication between microservices, internal network issues, or connectivity problems with the Payment Service Provider (PSP). Solution: Investigate communication-related infrastructure issues | “Failed Payment” | “Something went wrong with this payment. Please try again later” | "Go back” | | |||
| Represents errors associated with database operations within the system. | “Failed Payment” | “Something went wrong with this payment. Please try again later” | "Go back” |  | |||
| Represents errors caused by failures in third-party connections with external services necessary for the transaction, such as banks, payment gateways, identity verification services, etc. | “Failed Payment” | “Something went wrong with this payment. Please try again later” | "Go back” | | |||
| Represents errors that occur due to external factors not directly related to the internal infrastructure of the payment system. | “Failed Payment” | “Something went wrong with this payment. Please try again later” | "Go back” | | |||
| Represents errors that occur at the service layer, such as internal service failures, configuration issues, or other problems that prevent the service from functioning as expected. | “Failed Payment” | “Something went wrong with this payment. Please try again later” | "Go back” | | |||
| Represents errors that occur during the internal processing of payment transactions. Ex.: Payment not found for the given rbiOrderId | “Failed Payment” | “Something went wrong with this payment. Please try again later” | "Go back” | | |||
Traceability Matrix / Test Status
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 |
|
|
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 |
|
|
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 |
|
|
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 |
|
|
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. |
|
|
Add Comment