1. Objective
This document outlines the test strategy for integrating a new payment method, Waylet, via Paycomet. The purpose is to ensure that the integration works seamlessly and meets all functional and non-functional requirements.
2. Scope
Perform tests on a non-production test environment, e.g. Dev, QA or Staging.
Perform tests on the PROD environment.
3. Pre-Conditions - non-production test environment
3.1 WAYLET PRE-prod App
WAYLET PRE-prod App installed on a mobile device.
iOS via Testflight: https://testflight.apple.com/join/1QHOFclG
Android via APK: https://nextcloud.klikin.io/s/jEAQJr5NFg46w4E
After installing the app, create a Waylet account for test purposes:
Use “999999” on SMS code confirmation.
Send an e-mail to Waylet support (mail to: jose.rosa@waylet.es) asking for a recharge for your user.
Add credit cards with valid and invalid info. You can use the list of credit cards for testing by Paycoment: https://docs.paycomet.com/en/recursos/testcards
Add a test credit card with the correct info.
Add a test credit card with the wrong expiration date.
3.2 FEATURE FLAG CONFIGURATION
Waylet has a feature flag called Enable Waylet Paycomet which should be enabled.
If you do not have Launch Darkly access, coordinate with the development team to enable the feature flag before testing begins.
3.3 E2E Tests - Partners apps
In order to validate if the order was placed on the delivery app, the payment was approved or not, besides the WL app, you can access these partners' app:
RBI DMP.
Admin app tools.
Paycomet dashboard.
4. Test Cases
Test Case | Brand | Scenario | Pre-condition | How to execute | Expected result |
---|---|---|---|---|---|
1 | PLK ES | The new payment method is listed on the dropdown: Waylet |
|
|
|
2 | PLK ES | The new payment icon |
|
|
|
3 | PLK ES | Successful Payment Transaction - Waylet - credit card |
|
|
|
4 | PLK ES | Successful Payment Transaction - Waylet - balance |
|
|
|
5 | PLK ES | Interrupt payment process with Waylet - Order not placed |
|
|
|
6 | PLK ES | Payment failed - Waylet - Wrong credit card info |
|
|
|
7 | PLK ES | E2E testing: The order was received on the Delivery app (RBI DMP, Airtouch) |
|
|
|
8 | PLK ES | E2E testing: The order was received on Admin tools |
|
|
|
9 | PLK ES | E2E testing: The order was received on Paycomet dashboard |
|
|
|
5. Ensuring Test Security
The payment service provider, Paycomet, uses the same communication infrastructure for both development and production environments. The only difference between these environments is the URL and keys provided to the psp-paycomet-service. This ensures that tests conducted in the development environment accurately reflect the conditions of the production environment.
However, in the production environment, all data entered must be genuine, as this information is rigorously validated by the banking operators. Any invalid data can cause transaction failures or security blocks.
Add Comment