juspay/hyperswitch

[CYPRESS] : Add Fiserv Connector

Open

#5.902 aberto em 16 de set. de 2024

Ver no GitHub
 (3 comments) (0 reactions) (0 assignees)Rust (4.676 forks)batch import
E-mediumhacktoberfesthelp wantedjavascript

Métricas do repositório

Stars
 (42.690 stars)
Métricas de merge de PR
 (Mesclagem média 6d 22h) (213 fundiu PRs em 30d)

Description

Description:

This task involves adding a connector for the Fiserv functionality in Cypress. For reference, similar connectors have already been implemented in the repository. You can refer to the existing connectors here: https://github.com/juspay/hyperswitch/tree/main/cypress-tests/cypress/e2e/PaymentUtils

Pre-requisites:

  • Cypress is the testing framework that Hyperswitch is using to run automated tests. Having good grip on Javascript to work on Cypress is a must.
  • Please follow the README for guidelines on file structure, formatting and instructions on how to set up and run Cypress.

Steps:

  1. Add the Fiserv connector .js files under the PaymentUtils directory: PaymentUtils Directory

  2. Add the card details and corresponding test case functions for Fiserv, following the format used in the Cybersource.js connector.

  3. In the Fiserv connector, map the test cases and statuses properly. To do this, use the below dashboard credentials where Fiserv is already configured, test the flows, and then assign the correct statuses.

URL: https://integ.hyperswitch.io Username and Password: Please drop a comment requesting credentials. The Creds are only shared on request

Test Cases:

  • Add test cases only for card payments.

Postman Collection for reference

https://www.postman.com/altimetry-participant-63653904/hyperswitch

Note:

  • Test cases for other payment methods should be skipped.

  • The test cases are already written under PaymentTest:

    PaymentTest Directory.Just map the test cases and their statuses in the config.js file.

Submission Process:

  • Ask the maintainers for assignment of the issue, you can request for assignment by commenting on the issue itself.
  • Once assigned, submit a pull request (PR).
  • Maintainers will review and provide feedback, if any.
  • Maintainers can unassign issues due to inactivity, read more here.

Refer here for Terms and conditions for the contest.

Guia do colaborador