-
Notifications
You must be signed in to change notification settings - Fork 0
Home
Here is the summarized information for the test cases you provided:
-
DRPP-GP-09: FXP Timeout in Currency Conversion
- Objective: Validate FXP timeout handling across interscheme combinations.
- Expected Result: Transfer fails with a timeout error. Error is logged, monitored, and notified to the payer FSP.
-
DRPP-GP-10: FXP Processing Errors in Currency Conversion
- Objective: Validate FXP processing error handling across interscheme combinations.
- Expected Result: Transfer fails with a processing error. Error is logged, monitored, and notified to the payer FSP.
-
DRPP-GP-13: Quoting Service Timeout
- Objective: Validate quoting service timeout handling across schemes.
- Expected Result: Transfer fails with a timeout error. Error is logged, monitored, and notified to the payer FSP.
-
DRPP-GP-14: Quoting Service Processing Error
- Objective: Validate quoting service processing error handling across schemes.
- Expected Result: Transfer fails with a processing error. Error is logged, monitored, and notified to the payer FSP.
-
DRPP-GP-28: Self-Heal FX Transfer Flow - Payer Stuck in RESERVED FORWARDED - ABORTED ERROR State in FXP Scheme
- Objective: Validate successful transaction completion across interscheme combinations.
- Expected Result: Transaction completes successfully despite payer being stuck in an errored state. System self-heals.
-
DRPP-GP-15: FXP Timeout in Transfer Process
- Objective: Validate FXP timeout handling across interscheme combinations.
- Expected Result: Timeout error in FXP response without affecting DFSP positions.
-
DRPP-GP-16: FXP Processing Errors in Transfer Process
- Objective: Validate FXP processing error handling across interscheme combinations.
- Expected Result: Processing error in FXP response without affecting DFSP positions.
-
DRPP-GP-17: FXP Sends ABORTED State in Transfer Process
- Objective: Validate FXP ABORTED state response handling.
- Expected Result: ABORTED state in FXP response without affecting DFSP positions.
-
DRPP-GP-18: Transfer Service Timeout
- Objective: Validate transfer service timeout handling across interscheme combinations.
- Expected Result: Timeout error in transfer service response without affecting DFSP positions.
-
DRPP-GP-19: Transfer Service Processing Error
- Objective: Validate transfer service processing errors.
- Expected Result: Processing error in transfer service response without affecting DFSP positions.
-
DRPP-GP-20: Transfer Service Sends ABORTED State
- Objective: Validate transfer service ABORTED state response handling.
- Expected Result: ABORTED state in response without affecting DFSP positions.
-
DRPP-GP-21: Payee Transfer Service Timeout for Merchant Payment
- Objective: Handle Merchant Payment transfer service timeout.
- Expected Result: Timeout error without affecting DFSP positions.
-
DRPP-GP-22: Payee Transfer Service Processing Error for Merchant Payment
- Objective: Handle Merchant Payment transfer service processing errors.
- Expected Result: Processing error without affecting DFSP positions.
-
DRPP-GP-23: Payee Transfer Service Sends ABORTED State for Merchant Payment
- Objective: Handle Merchant Payment transfer service ABORTED state responses.
- Expected Result: ABORTED state without impacting DFSP positions.
-
DRPP-GP-01: Send Money (Source Currency, Multiple FXPs)
- Objective: Validate successful transaction completion.
- Expected Result: Successful transaction.
-
DRPP-GP-03: Merchant Payment (Target Currency, Multiple FXPs)
- Objective: Validate successful merchant payment completion.
- Expected Result: Successful merchant payment.
-
DRPP-GP-04: Party Does Not Exist in Any Scheme
- Objective: Ensure proper error handling when a party is not found.
- Expected Result: Error: Party Not Found.
-
DRPP-GP-05: Party Exists in Multiple Schemes for Different Currencies
- Objective: Ensure correct resolution when a party spans multiple schemes.
- Expected Result: Correct resolution with configured currencies returned.
-
DRPP-GP-06: Party Moves from One DFSP to Another in a Single Scheme
- Objective: Ensure smooth resolution during party movement.
- Expected Result: Smooth transition with correct DFSP returned.
-
DRPP-GP-08: DFSP Handling Error When Others Return Party Not Found
- Objective: Handle errors when a party's DFSP fails while others return "not found."
- Expected Result: Proper error handling, and error is sent back to the payer.
-
DRPP-GP-12: Test Payer for Max Outgoing Transaction (COMESA Scheme)
- Objective: Validate enforcement of COMESA scheme rules for outgoing amounts.
- Expected Result: Transfer rejected with error code 4200: "Payer limit error."
-
DRPP-GP-11: Test Payee for Max Incoming Transaction (COMESA Scheme)
- Objective: Validate enforcement of COMESA scheme rules for incoming transactions.
- Expected Result: Transfer rejected with error code 4200: "Payee limit error."
-
Test for Max Payee Outgoing in Regional Scheme
- Objective: Validate COMESA rules for max outgoing in regional schemes.
- Expected Result: Transfer rejected with error code 4200.
-
DRPP-GP-24: Self-Heal Transfer Flow Stuck in RESERVED FORWARDED - COMMITTED State in Payee Scheme
- Objective: Validate successful transaction completion.
- Expected Result: Successful self-healed transaction completion.
-
DRPP-GP-25: Self-Heal Transfer Flow Stuck in RESERVED FORWARDED - ABORTED ERROR State in Payee Scheme
- Objective: Validate error callback for errored state.
- Expected Result: Successful error callback with correct error code.
-
DRPP-GP-26: Self-Heal Transfer Flow Stuck in RESERVED FORWARDED - COMMITTED State (Payee + Regional Scheme)
- Objective: Validate successful transaction completion for regional schemes.
- Expected Result: Successful transaction self-heal.
-
**DRPP-GP-27: Self-Heal Transfer Flow Stuck in RESERVED FORWAR