SWIFT Community
For SQE’s (Software Quality Engineers) to collaborate and share ideas and experiences
Organizer:
- Organized by
-
-
Sibongile SWIFT Learning Path
-
Sibongile SWIFT Learning Path
Swift Direct Debit Payment Process
FEATURE: Authorized Direct Debit
1. Scenario: Request for Pre-Authorized Direct Debit Mandate
Given a customer applies for a request to add an Authorization for a Pre-Authorized Direct Debit Mandate
When the Debtors bank receives a request to add an Authorization for a Pre-Authorized Direct Debit Mandate
Then sign a Direct Debit contract for Pre-Authorized Mandate between Debtors bank and Customer
AND send request to Creditor
AND Creditor to send signed contract to Creditors’ bank informing of the mandate between Creditor and Debtor
AND Debit the Debtors bank account
2. Scenario: Pre-Authorized Direct Debit Mandate exists
Given that a Pre-Authorized Direct Debit Mandate between Creditor Bank and Debtors exits
When a Direct Debit instruction is sent to the Debtors’ bank for payment from Creditor’s bank
Then send instruction (MT104) with Pre-Authorized Mandate to Debtors Bank
AND collect required funds within allowed limit
AND required currency
AND follow the domestic direct debit rules of the receiving country to specify messages
3. Scenario: Pre-Authorized Direct Debit Failure
Given that a Pre-Authorized Direct Debit Mandate exists
When a Direct Debit instruction (MT104) is sent to the Debtors’ bank for payment from Creditor’s bank
AND there are no funds in Debtors’ bank account
Then Debtors Bank rejects Direct Debit instruction
AND if rejected items exceed allowed limit
Then inform Creditors bank by fax or telex
Given that no Mandate exists between Debtor and Creditor
Then reject Direct Debit instruction
Given that a debtor sends and instruction to their bank to revoke their mandate
Then No Revocation allowed
4. Scenario: Non-Pre-Authorized Direct Debit
Given that no Pre-Authorized Direct Debit Mandate exists
When a Direct Debit instruction is sent to the Debtors’ bank for payment from Creditor’s bank
Then send instruction (MT104) to Debtors Bank
AND collect required funds within allowed limit
AND required currency
AND follow the domestic direct debit rules of the receiving country to specify messages
5. Scenario: Non Pre-Authorized Direct Debit Failure
Given that no Pre-Authorized Direct Debit Mandate exists
When a Direct Debit instruction (MT104) is sent to the Debtors’ bank for payment from Creditor’s bank
AND there are no funds in Debtors’ bank account
Then Debtors Bank rejects Direct Debit instruction
AND if rejected items exceed allowed limit
Then inform Creditors bank
Given that a debtor sends and instruction to their bank to revoke their mandate
When their mandate is successfully revoked by their bank
Then Revocation is allowed within a certain time limit between Debtor and Debtors bank
-
2 Replies
-
Sibongile, this is a great start. Check 3 and 5 which are not in line with the standard and look like they could be separate scenarios.
-
I’m thinking the same as Jerome. From testing days I always avoid AND / OR as they create complicated testing paths that overlook bugs. Coming up with a recipe – in Scenario 1 the AND lists actions or tasks. This is a simple path and is processed sequentially. In 3 and 5 the AND represents rules and multiple scenarios. Which means a decision table. In 5 we have the rule no funds and the rule exceed allowed limit. Thus, as stated in 5, we have 4 different scenarios. They are:- exceed funds and not the limit, exceed funds and the limit, not exceed funds and exceed limit and not exceed funds and not exceed limit. Whereas having them as separate scenarios we have exceed funds and exceed limit. Remember this is not testing. It is an example of what happens in business and identifying gaps in specifications.
-
Log in to reply.