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

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

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

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

Configurations

  • APIs: Test endpoints configured to simulate the production environment.

Prerequisites

  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 PayPal

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

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

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

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

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

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

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

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

API Endpoints

1.

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)

Reports and Logs

(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.

Conclusion

(not ready yet)

  • No labels