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 7 Next »

Document Status

WORK-IN-PROGRESS

Document Owner(s)

Malzac, Alice

Reviewers

Introduction

This documentation describes the process of automating regression tests for the RBI's payment system. The automation aims to ensure that new code changes do not introduce errors in existing functionalities.

Objective

The primary objective of this automation is to validate the integrity of the payment system after each code change or update, ensuring that all payment flows function as expected.

Test Environment

→ PLK ES & BK PT

  • Development Env: Used for continuous development and initial testing.

  • Staging Env: Used for automated testing before any release.

  • QA Env: Used for automated testing before any release.

Configurations

  1. Node.js: Ensure you have Node.js installed. You can download it from Node.js.

  2. Cypress: Install Cypress via npm.

Test Scenarios

  1. Check if the user is able to place an order using Cash → Already implemented by EMEA

  2. Check if the user is able to place an order using Sodexo

    1. Access the whitelabel app.

    2. Go to checkout page by delivery flow.

    3. On payment screen, select Sodexo

    4. Select it and place the order

    5. Check if the payment method used is the same as step c

  3. Check if the user is able to place an order using Cheque Gourmet

    1. Access the whitelabel app.

    2. Go to checkout page by delivery flow.

    3. On payment screen, select Cheque Gourmet

    4. Select it and place the order

    5. Check if the payment method used is the same as step c

  4. Check if the user is able to place an order using Cheque Gourmet Voucher

    1. Access the whitelabel app.

    2. Go to checkout page by delivery flow.

    3. On payment screen, select Cheque Gourmet Voucher

    4. Select it and place the order

    5. Check if the payment method used is the same as step c

  5. Check if the user is able to place an order using Cart on Delivery

    1. Access the whitelabel app.

    2. Go to checkout page by delivery flow.

    3. On payment screen, select Cart on Delivery

    4. Select it and place the order

    5. Check if the payment method used is the same as step c

  6. Check if the user is able to place an order using PayPal

    1. Access the whitelabel app.

    2. Go to checkout page by delivery flow.

    3. On payment screen, select PayPal

    4. Select it and place the order

    5. Check if the payment method used is the same as step c

  7. Check if the user is able to place an order using Bizum

    1. Access the whitelabel app.

    2. Go to checkout page by delivery flow.

    3. On payment screen, select Bizum

    4. Select it and place the order

    5. Check if the payment method used is the same as step c

  8. Check if the user is able to place an order using Apple Pay

    1. Access the whitelabel app.

    2. Go to checkout page by delivery flow.

    3. On payment screen, select Apple Pay

    4. Select it and place the order

    5. Check if the payment method used is the same as step c

  9. Check if the user is able to place an order using Waylet

    1. Access the whitelabel app.

    2. Go to checkout page by delivery flow.

    3. On payment screen, select Waylet

    4. Select it and place the order

    5. Check if the payment method used is the same as step c

  10. Check if you can give a refund

  11. Check if you can cancel a payment

Test Execution

  1. Access the repository: https://github.com/rbilabs/intl-whitelabel-app/tree/master and go to workspaces/cypress-iberia folder (not ready yet)

  2. On the terminal:

    1. Run Cypress in Interactive Mode: npx cypress open

    2. Run Cypress in Headless Mode: npx cypress run

  3. Looks like this: (not ready yet)

Maintenance and Updates

  • Update Dependencies: Regularly update all dependencies to their latest versions.

  • Review Test Scripts: Periodically review and update test scripts to cover new features and changes.

  • Monitor Test Runs: Regularly monitor automated test runs to ensure they are functioning correctly and addressing any issues promptly.

Reports and Logs

(not ready yet)

Conclusion

(not ready yet)

  • No labels

0 Comments

You are not logged in. Any changes you make will be marked as anonymous. You may want to Log In if you already have an account.