-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(cypress): add multiple creds and flags support #6588
base: main
Are you sure you want to change the base?
Conversation
2dba2c0
to
c4d8809
Compare
d061ad6
to
22feccb
Compare
this is done so that regressions may not arise
this is a huge change! this will make it possible for us to select connector based on the need. say, trustpay refunds only work on a specific connector credential, pass the spec name, done.
…ed-cypress * 'main' of github.com:juspay/hyperswitch: feat(payment_methods_v2): implement a barebones version of list customer payment methods v2 (#6649) ci: update ntid card expiry (#6714) chore(version): 2024.12.02.1 fix(openapi): Revert Standardise API naming scheme for V2 Dashboard Changes (#6712)
}); | ||
|
||
it("retrieve-payment-call-test", () => { | ||
cy.retrievePaymentCallTest(globalState); | ||
const data = getConnectorDetails(globalState.get("connectorId"))[ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is the need of this ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
glad you asked. data exist only to fetch the Configs
and nothing else. in the support/commands.js
(image attached below), we're extracting Configs
from data
. this is done specifically keeping CONNECTOR_CREDENTIAL
in mind so that we can pass mca_id
directly which is used in verification (assertion check).
the entire field can be removed if we stop doing mca_id
check.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are we not verifying the payment status ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes. remove this mca_id check?
172a8d1
Type of Change
Description
This PR introduces 2 new features:
closes #6645 (check this issue for detailed documentation / flow / explanation)
Additional Changes
Motivation and Context
How did you test it?
Only Cybersource with
multiple creds
(takes only from firstconnector_1
):Cybersource with
multiple creds
(along withincremental auth
):(incremental auth fails from the connector's end and hence 4 failures)
Stripe:
Wise:
PML:
have disabled incremental auth from executing:
trustpay refunds (multiple creds):
i commented iDEAL redirections to check, error is being thrown from connector's end and there's nothing much i can do:
Checklist
prettier . --write
cargo clippy