CBSNexora/cbsnexora-backend
4
0
Fork 0
Code Issues Pull Requests Actions 37 Packages Projects Releases Wiki Activity

FINERACT-2070: E2E testcase migration - feature files - pt1

Browse Source
This commit is contained in:
Peter Kovacs
2024-11-10 14:35:18 +01:00
committed by Adam Saghy
parent 64976f1eb4
commit 6770352da8
6 changed files with 185 additions and 194 deletions
Download Patch File Download Diff File Expand all files Collapse all files
fineract-e2e-tests-runner/src/test/resources/features/0_COB.feature
+16 -16
View File
@@ -1,7 +1,7 @@
@COBFeature
Feature: COBFeature
@Skip
@TestRailId:C2501
Scenario: As an admin I would like to see that last closed business date got updated after COB catch up job finished
When Admin sets the business date to "01 January 2022"
When Admin creates a client with random data
@@ -22,7 +22,7 @@ Feature: COBFeature
Then Loan status will be "CLOSED_OBLIGATIONS_MET"
@Skip
@TestRailId:C2681
Scenario: As an admin I would like to check that the Delinquency bucket set on the loan correctly when the arrears setting is 3 on the product
When Admin sets the business date to "1 January 2022"
When Admin creates a client with random data
@@ -33,7 +33,7 @@ Feature: COBFeature
When Admin runs COB job
Then Admin checks that delinquency range is: "RANGE_1" and has delinquentDate "2022-02-03"
@Skip
@TestRailId:C2791
Scenario: Verify that COB processes loans which are not closed/overpaid and has a last_closed_business_date exactly 1 day behind COB date
When Admin sets the business date to "01 July 2023"
When Admin creates a client with random data
@@ -49,7 +49,7 @@ Feature: COBFeature
When Admin runs COB job
Then Admin checks that last closed business date of loan is "02 July 2023"
@TestRailId:C2792
Scenario: Verify that COB doesn’t touch loans with last closed business date behind COB date
When Admin sets the business date to "01 July 2023"
When Admin creates a client with random data
@@ -58,23 +58,23 @@ Feature: COBFeature
When Admin successfully disburse the loan on "01 July 2023" with "1000" EUR transaction amount
Then Loan status will be "ACTIVE"
Then Admin checks that last closed business date of loan is "null"
When Admin sets the business date to "09 August 2023"
When Admin sets the business date to "10 August 2023"
When Admin runs inline COB job for Loan
Then Admin checks that last closed business date of loan is "08 August 2023"
Then Admin checks that last closed business date of loan is "09 August 2023"
Then Admin checks that delinquency range is: "RANGE_3" and has delinquentDate "2023-08-03"
Then Loan delinquency history has the following details:
| Range (Classification) | Added on date | Lifted on date |
| RANGE_3 | 09 August 2023 | |
| RANGE_3 | 10 August 2023 | |
| RANGE_1 | 04 August 2023 | 09 August 2023 |
When Admin sets the business date to "12 August 2023"
When Admin runs COB job
Then Admin checks that last closed business date of loan is "08 August 2023"
Then Admin checks that last closed business date of loan is "09 August 2023"
Then Loan delinquency history has the following details:
| Range (Classification) | Added on date | Lifted on date |
| RANGE_3 | 09 August 2023 | |
| RANGE_3 | 10 August 2023 | |
| RANGE_1 | 04 August 2023 | 09 August 2023 |
@TestRailId:C2793
Scenario: Verify that COB doesn’t touch CLOSED loans
When Admin sets the business date to "01 July 2023"
When Admin creates a client with random data
@@ -106,7 +106,7 @@ Feature: COBFeature
| RANGE_3 | 10 August 2023 | 10 August 2023 |
| RANGE_1 | 04 August 2023 | 09 August 2023 |
@TestRailId:C2794
Scenario: Verify that COB doesn’t touch OVERPAID loans
When Admin sets the business date to "01 July 2023"
When Admin creates a client with random data
@@ -138,7 +138,7 @@ Feature: COBFeature
| RANGE_3 | 10 August 2023 | 10 August 2023 |
| RANGE_1 | 04 August 2023 | 09 August 2023 |
@Skip
@Skip @TestRailId:C2795
Scenario: Verify that COB catch up runs properly on loan which is behind date because of locked with error
When Admin sets the business date to "01 January 2022"
When Admin creates a client with random data
@@ -161,7 +161,7 @@ Feature: COBFeature
And Customer makes "AUTOPAY" repayment on "05 January 2022" with 1000 EUR transaction amount
Then Loan status will be "CLOSED_OBLIGATIONS_MET"
@TestRailId:C2796
Scenario: Verify that after COB runs there are no unreleased loan locks
When Admin sets the business date to "01 July 2023"
When Admin creates a client with random data
@@ -174,7 +174,7 @@ Feature: COBFeature
When Admin runs COB job
Then The loan account is not locked
@Skip
@TestRailId:C2797
Scenario: Verify that Inline COB is executed for stuck loans - when payment happened on a loan with last closed business date in the past, COB got executed before the repayment
When Admin sets the business date to "01 July 2023"
When Admin creates a client with random data
@@ -194,7 +194,7 @@ Feature: COBFeature
# On a hard locked loan, in case of the lock has an error message, payment by a non-bypass user should trigger inlineCob and it should be executed
# this functionality is not implemented yet
@Skip
@Skip @TestRailId:C2798
Scenario: Verify that Inline COB is executed for stuck loans - when payment happened on a locked loan COB got executed before the repayment
When Admin sets the business date to "01 July 2023"
When Admin creates a client with random data
@@ -213,7 +213,7 @@ Feature: COBFeature
When Created user makes externalID controlled "AUTOPAY" repayment on "04 July 2023" with 500 EUR transaction amount
Then Admin checks that last closed business date of loan is "03 July 2023"
@AdvancedPaymentAllocation
@TestRailId:C3044 @AdvancedPaymentAllocation
Scenario: Verify that LoanAccountCustomSnapshotBusinessEvent is created with proper business date when installment is due date and COB runs
Given Admin puts CHECK_DUE_INSTALLMENTS job into LOAN_CLOSE_OF_BUSINESS workflow
When Admin sets the business date to "01 January 2024"
fineract-e2e-tests-runner/src/test/resources/features/AssetExternalization.feature
+145 -136
View File
@@ -1,7 +1,7 @@
@AssetExternalizationFeature
Feature: Asset Externalization
@TestRailId:C2722
Scenario: Verify that all fields and values are correct in case of a SALES request by loan id and user-generated transferExternalId
Given Admin puts EXTERNAL_ASSET_OWNER_TRANSFER job into LOAN_CLOSE_OF_BUSINESS workflow
When Admin sets the business date to "1 May 2023"
@@ -26,7 +26,7 @@ Feature: Asset Externalization
Then Asset externalization details has the generated transferExternalId
Then Admin removes EXTERNAL_ASSET_OWNER_TRANSFER job from LOAN_CLOSE_OF_BUSINESS workflow
@TestRailId:C2723
Scenario: Verify that all fields and values are correct in case of a SALES request by loan id system-generated transferExternalId
Given Admin puts EXTERNAL_ASSET_OWNER_TRANSFER job into LOAN_CLOSE_OF_BUSINESS workflow
When Admin sets the business date to "1 May 2023"
@@ -51,7 +51,7 @@ Feature: Asset Externalization
Then Asset externalization details has the generated transferExternalId
Then Admin removes EXTERNAL_ASSET_OWNER_TRANSFER job from LOAN_CLOSE_OF_BUSINESS workflow
@TestRailId:C2724
Scenario: Verify that all fields and values are correct in case of a SALES request by loan external id user-generated transferExternalId
Given Admin puts EXTERNAL_ASSET_OWNER_TRANSFER job into LOAN_CLOSE_OF_BUSINESS workflow
When Admin sets the business date to "1 May 2023"
@@ -76,7 +76,7 @@ Feature: Asset Externalization
Then Asset externalization details has the generated transferExternalId
Then Admin removes EXTERNAL_ASSET_OWNER_TRANSFER job from LOAN_CLOSE_OF_BUSINESS workflow
@TestRailId:C2725
Scenario: Verify that all fields and values are correct in case of a SALES request by loan external id system-generated transferExternalId
Given Admin puts EXTERNAL_ASSET_OWNER_TRANSFER job into LOAN_CLOSE_OF_BUSINESS workflow
When Admin sets the business date to "1 May 2023"
@@ -101,7 +101,7 @@ Feature: Asset Externalization
Then Asset externalization details has the generated transferExternalId
Then Admin removes EXTERNAL_ASSET_OWNER_TRANSFER job from LOAN_CLOSE_OF_BUSINESS workflow
@TestRailId:C2727
Scenario: Verify that Asset externalization details are correct after CoB in case of a SALES request by loan id
Given Admin puts EXTERNAL_ASSET_OWNER_TRANSFER job into LOAN_CLOSE_OF_BUSINESS workflow
When Admin sets the business date to "1 May 2023"
@@ -125,7 +125,7 @@ Feature: Asset Externalization
| 2023-05-21 | 1 | ACTIVE | 2023-05-22 | 9999-12-31 | SALE |
Then Admin removes EXTERNAL_ASSET_OWNER_TRANSFER job from LOAN_CLOSE_OF_BUSINESS workflow
@TestRailId:C2729
Scenario: Verify that Asset externalization details has the correct data in case of a BUYBACK request placed before the settlementDate with a same settlementDate as the sales one
Given Admin puts EXTERNAL_ASSET_OWNER_TRANSFER job into LOAN_CLOSE_OF_BUSINESS workflow
When Admin sets the business date to "1 May 2023"
@@ -161,7 +161,7 @@ Feature: Asset Externalization
| 2023-05-21 | 1 | CANCELLED | 2023-05-21 | 2023-05-21 | BUYBACK |
Then Admin removes EXTERNAL_ASSET_OWNER_TRANSFER job from LOAN_CLOSE_OF_BUSINESS workflow
@TestRailId:C2730
Scenario: Verify that Asset externalization details has the correct data in case of a BUYBACK request placed on a business date before the settlementDate of sales request and with a settlementDate for buyback after the sales got active
Given Admin puts EXTERNAL_ASSET_OWNER_TRANSFER job into LOAN_CLOSE_OF_BUSINESS workflow
When Admin sets the business date to "1 May 2023"
@@ -202,7 +202,7 @@ Feature: Asset Externalization
| 2023-05-21 | 1 | ACTIVE | 2023-05-22 | 2023-05-30 | SALE |
Then Admin removes EXTERNAL_ASSET_OWNER_TRANSFER job from LOAN_CLOSE_OF_BUSINESS workflow
@TestRailId:C2731
Scenario: Verify that Asset externalization details has the correct data in case of a BUYBACK request placed after the settlementDate
Given Admin puts EXTERNAL_ASSET_OWNER_TRANSFER job into LOAN_CLOSE_OF_BUSINESS workflow
When Admin sets the business date to "1 May 2023"
@@ -247,7 +247,7 @@ Feature: Asset Externalization
| 2023-05-30 | 1 | BUYBACK | 2023-05-25 | 2023-05-30 | BUYBACK |
Then Admin removes EXTERNAL_ASSET_OWNER_TRANSFER job from LOAN_CLOSE_OF_BUSINESS workflow
@TestRailId:C2732
Scenario: Verify that BUYBACK request on a loan with PENDING ownership where BUYBACK settlement date is earlier than SALE settlement date results an error
Given Admin puts EXTERNAL_ASSET_OWNER_TRANSFER job into LOAN_CLOSE_OF_BUSINESS workflow
When Admin sets the business date to "1 May 2023"
@@ -270,7 +270,7 @@ Feature: Asset Externalization
| buyback | 2023-05-15 |
Then Admin removes EXTERNAL_ASSET_OWNER_TRANSFER job from LOAN_CLOSE_OF_BUSINESS workflow
@TestRailId:C2733
Scenario: Verify that SALES request on a fully paid loan results an error
Given Admin puts EXTERNAL_ASSET_OWNER_TRANSFER job into LOAN_CLOSE_OF_BUSINESS workflow
When Admin sets the business date to "1 May 2023"
@@ -286,7 +286,7 @@ Feature: Asset Externalization
| sale | 2023-05-21 | 1 |
Then Admin removes EXTERNAL_ASSET_OWNER_TRANSFER job from LOAN_CLOSE_OF_BUSINESS workflow
@TestRailId:C2734
Scenario: Verify that SALES request on an overpaid loan results an error
Given Admin puts EXTERNAL_ASSET_OWNER_TRANSFER job into LOAN_CLOSE_OF_BUSINESS workflow
When Admin sets the business date to "1 May 2023"
@@ -302,7 +302,7 @@ Feature: Asset Externalization
| sale | 2023-05-21 | 1 |
Then Admin removes EXTERNAL_ASSET_OWNER_TRANSFER job from LOAN_CLOSE_OF_BUSINESS workflow
@TestRailId:C2735
Scenario: Verify that SALES request on a loan with ACTIVE ownership results an error
Given Admin puts EXTERNAL_ASSET_OWNER_TRANSFER job into LOAN_CLOSE_OF_BUSINESS workflow
When Admin sets the business date to "1 May 2023"
@@ -332,7 +332,7 @@ Feature: Asset Externalization
| sale | 2023-05-30 | 1 |
Then Admin removes EXTERNAL_ASSET_OWNER_TRANSFER job from LOAN_CLOSE_OF_BUSINESS workflow
@TestRailId:C2736
Scenario: Verify that BUYBACK request on a fully paid loan can be done successfully
Given Admin puts EXTERNAL_ASSET_OWNER_TRANSFER job into LOAN_CLOSE_OF_BUSINESS workflow
When Admin sets the business date to "1 May 2023"
@@ -369,7 +369,7 @@ Feature: Asset Externalization
| 2023-05-30 | 1 | BUYBACK | 2023-05-25 | 9999-12-31 | BUYBACK |
Then Admin removes EXTERNAL_ASSET_OWNER_TRANSFER job from LOAN_CLOSE_OF_BUSINESS workflow
@TestRailId:C2737
Scenario: Verify that BUYBACK request on an overpaid loan can be done successfully
Given Admin puts EXTERNAL_ASSET_OWNER_TRANSFER job into LOAN_CLOSE_OF_BUSINESS workflow
When Admin sets the business date to "1 May 2023"
@@ -406,7 +406,7 @@ Feature: Asset Externalization
| 2023-05-30 | 1 | BUYBACK | 2023-05-25 | 9999-12-31 | BUYBACK |
Then Admin removes EXTERNAL_ASSET_OWNER_TRANSFER job from LOAN_CLOSE_OF_BUSINESS workflow
@TestRailId:C2738
Scenario: Verify that BUYBACK request on a loan with INACTIVE ownership results an error
Given Admin puts EXTERNAL_ASSET_OWNER_TRANSFER job into LOAN_CLOSE_OF_BUSINESS workflow
When Admin sets the business date to "1 May 2023"
@@ -420,7 +420,7 @@ Feature: Asset Externalization
| buyback | 2023-05-21 | |
Then Admin removes EXTERNAL_ASSET_OWNER_TRANSFER job from LOAN_CLOSE_OF_BUSINESS workflow
@TestRailId:C2739
Scenario: Verify that SALES request can NOT be placed on a loan which is not APPROVED yet
Given Admin puts EXTERNAL_ASSET_OWNER_TRANSFER job into LOAN_CLOSE_OF_BUSINESS workflow
When Admin sets the business date to "1 May 2023"
@@ -432,7 +432,7 @@ Feature: Asset Externalization
| sale | 2023-05-30 | 1 |
Then Admin removes EXTERNAL_ASSET_OWNER_TRANSFER job from LOAN_CLOSE_OF_BUSINESS workflow
@TestRailId:C2740
Scenario: Verify that SALES request can NOT be placed on a loan which is not DISBURSED yet
Given Admin puts EXTERNAL_ASSET_OWNER_TRANSFER job into LOAN_CLOSE_OF_BUSINESS workflow
When Admin sets the business date to "1 May 2023"
@@ -445,7 +445,7 @@ Feature: Asset Externalization
| sale | 2023-05-30 | 1 |
Then Admin removes EXTERNAL_ASSET_OWNER_TRANSFER job from LOAN_CLOSE_OF_BUSINESS workflow
@TestRailId:C2741
Scenario: Verify that SALES request on a loan with PENDING ownership results an error
Given Admin puts EXTERNAL_ASSET_OWNER_TRANSFER job into LOAN_CLOSE_OF_BUSINESS workflow
When Admin sets the business date to "1 May 2023"
@@ -468,7 +468,7 @@ Feature: Asset Externalization
| sale | 2023-05-30 | 1 |
Then Admin removes EXTERNAL_ASSET_OWNER_TRANSFER job from LOAN_CLOSE_OF_BUSINESS workflow
@TestRailId:C2742
Scenario: Verify that SALES with settlement date earlier than actual business date results an error
Given Admin puts EXTERNAL_ASSET_OWNER_TRANSFER job into LOAN_CLOSE_OF_BUSINESS workflow
When Admin sets the business date to "1 May 2023"
@@ -482,7 +482,7 @@ Feature: Asset Externalization
| sale | 2023-04-21 | 1 |
Then Admin removes EXTERNAL_ASSET_OWNER_TRANSFER job from LOAN_CLOSE_OF_BUSINESS workflow
@TestRailId:C2743
Scenario: Verify that SALES with null owner external id results an error
Given Admin puts EXTERNAL_ASSET_OWNER_TRANSFER job into LOAN_CLOSE_OF_BUSINESS workflow
When Admin sets the business date to "1 May 2023"
@@ -496,7 +496,7 @@ Feature: Asset Externalization
| 2023-05-21 | 1 |
Then Admin removes EXTERNAL_ASSET_OWNER_TRANSFER job from LOAN_CLOSE_OF_BUSINESS workflow
@TestRailId:C2744
Scenario: Verify that SALES with null purchase price ratio results an error
Given Admin puts EXTERNAL_ASSET_OWNER_TRANSFER job into LOAN_CLOSE_OF_BUSINESS workflow
When Admin sets the business date to "1 May 2023"
@@ -510,7 +510,7 @@ Feature: Asset Externalization
| sale | 2023-05-21 | |
Then Admin removes EXTERNAL_ASSET_OWNER_TRANSFER job from LOAN_CLOSE_OF_BUSINESS workflow
@TestRailId:C2745
Scenario: Verify that SALES with null settlement date results an error
Given Admin puts EXTERNAL_ASSET_OWNER_TRANSFER job into LOAN_CLOSE_OF_BUSINESS workflow
When Admin sets the business date to "1 May 2023"
@@ -524,7 +524,7 @@ Feature: Asset Externalization
| sale | | 1 |
Then Admin removes EXTERNAL_ASSET_OWNER_TRANSFER job from LOAN_CLOSE_OF_BUSINESS workflow
@TestRailId:C2746
Scenario: Verify that BUYBACK request on a loan with PENDING BUYBACK ownership result an error
Given Admin puts EXTERNAL_ASSET_OWNER_TRANSFER job into LOAN_CLOSE_OF_BUSINESS workflow
When Admin sets the business date to "1 May 2023"
@@ -565,7 +565,7 @@ Feature: Asset Externalization
| buyback | 2023-05-30 | |
Then Admin removes EXTERNAL_ASSET_OWNER_TRANSFER job from LOAN_CLOSE_OF_BUSINESS workflow
@TestRailId:C2747
Scenario: Verify that BUYBACK with settlement date earlier than actual business date results an error
Given Admin puts EXTERNAL_ASSET_OWNER_TRANSFER job into LOAN_CLOSE_OF_BUSINESS workflow
When Admin sets the business date to "1 May 2023"
@@ -596,7 +596,7 @@ Feature: Asset Externalization
| buyback | 2023-05-21 | |
Then Admin removes EXTERNAL_ASSET_OWNER_TRANSFER job from LOAN_CLOSE_OF_BUSINESS workflow
@TestRailId:C2748
Scenario: Verify that BUYBACK with ownerExternalId=NULL can be placed, and results a 200OK response
Given Admin puts EXTERNAL_ASSET_OWNER_TRANSFER job into LOAN_CLOSE_OF_BUSINESS workflow
When Admin sets the business date to "1 May 2023"
@@ -630,7 +630,7 @@ Feature: Asset Externalization
| 2023-05-30 | 1 | BUYBACK | 2023-05-25 | 9999-12-31 | BUYBACK |
Then Admin removes EXTERNAL_ASSET_OWNER_TRANSFER job from LOAN_CLOSE_OF_BUSINESS workflow
@TestRailId:C2749
Scenario: Verify that BUYBACK with purchasePriceRatio=NULL can be placed, and results a 200OK response
Given Admin puts EXTERNAL_ASSET_OWNER_TRANSFER job into LOAN_CLOSE_OF_BUSINESS workflow
When Admin sets the business date to "1 May 2023"
@@ -666,7 +666,7 @@ Feature: Asset Externalization
| 2023-05-30 | 1 | BUYBACK | 2023-05-25 | 9999-12-31 | BUYBACK |
Then Admin removes EXTERNAL_ASSET_OWNER_TRANSFER job from LOAN_CLOSE_OF_BUSINESS workflow
@TestRailId:C2750
Scenario: Verify that SALES with null settlement date results an error
Given Admin puts EXTERNAL_ASSET_OWNER_TRANSFER job into LOAN_CLOSE_OF_BUSINESS workflow
When Admin sets the business date to "1 May 2023"
@@ -697,7 +697,7 @@ Feature: Asset Externalization
| buyback | | |
Then Admin removes EXTERNAL_ASSET_OWNER_TRANSFER job from LOAN_CLOSE_OF_BUSINESS workflow
@AssetExternalizationJournalEntry
@TestRailId:C2751 @AssetExternalizationJournalEntry
Scenario: Verify that Asset externalization SALES and BUYBACK has the correct Journal entries: no other transactions
Given Admin puts EXTERNAL_ASSET_OWNER_TRANSFER job into LOAN_CLOSE_OF_BUSINESS workflow
When Admin sets the business date to "1 May 2023"
@@ -759,7 +759,7 @@ Feature: Asset Externalization
| ASSET | 112601 | Loans Receivable | CREDIT | 1000.00 |
Then Admin removes EXTERNAL_ASSET_OWNER_TRANSFER job from LOAN_CLOSE_OF_BUSINESS workflow
@AssetExternalizationJournalEntry
@TestRailId:C2752 @AssetExternalizationJournalEntry
Scenario: Verify that Asset externalization SALES and BUYBACK has the correct Journal entries: fee applied before sale, and penalty applied before buyback
Given Admin puts EXTERNAL_ASSET_OWNER_TRANSFER job into LOAN_CLOSE_OF_BUSINESS workflow
When Admin sets the business date to "1 May 2023"
@@ -836,7 +836,7 @@ Feature: Asset Externalization
| ASSET | 112603 | Interest/Fee Receivable | CREDIT | 30.00 |
Then Admin removes EXTERNAL_ASSET_OWNER_TRANSFER job from LOAN_CLOSE_OF_BUSINESS workflow
@AssetExternalizationJournalEntry
@TestRailId:C2753 @AssetExternalizationJournalEntry
Scenario: Verify that Asset externalization SALES and BUYBACK has the correct Journal entries: Repyment while status is ACTIVE
Given Admin puts EXTERNAL_ASSET_OWNER_TRANSFER job into LOAN_CLOSE_OF_BUSINESS workflow
When Admin sets the business date to "1 May 2023"
@@ -901,7 +901,7 @@ Feature: Asset Externalization
| ASSET | 112601 | Loans Receivable | CREDIT | 800.00 |
Then Admin removes EXTERNAL_ASSET_OWNER_TRANSFER job from LOAN_CLOSE_OF_BUSINESS workflow
@AssetExternalizationJournalEntry
@TestRailId:C2754 @AssetExternalizationJournalEntry
Scenario: Verify that Asset externalization SALES and BUYBACK has the correct Journal entries: GOODWILL_CREDIT transaction while status is ACTIVE
Given Admin puts EXTERNAL_ASSET_OWNER_TRANSFER job into LOAN_CLOSE_OF_BUSINESS workflow
When Admin sets the business date to "1 May 2023"
@@ -966,7 +966,7 @@ Feature: Asset Externalization
| ASSET | 112601 | Loans Receivable | CREDIT | 800.00 |
Then Admin removes EXTERNAL_ASSET_OWNER_TRANSFER job from LOAN_CLOSE_OF_BUSINESS workflow
@AssetExternalizationJournalEntry
@TestRailId:C2755 @AssetExternalizationJournalEntry
Scenario: Verify that Asset externalization SALES and BUYBACK has the correct Journal entries: MERCHANT_ISSUED_REFUND transaction while status is ACTIVE
Given Admin puts EXTERNAL_ASSET_OWNER_TRANSFER job into LOAN_CLOSE_OF_BUSINESS workflow
When Admin sets the business date to "1 May 2023"
@@ -1031,7 +1031,7 @@ Feature: Asset Externalization
| ASSET | 112601 | Loans Receivable | CREDIT | 800.00 |
Then Admin removes EXTERNAL_ASSET_OWNER_TRANSFER job from LOAN_CLOSE_OF_BUSINESS workflow
@AssetExternalizationJournalEntry
@TestRailId:C2756 @AssetExternalizationJournalEntry
Scenario: Verify that Asset externalization SALES and BUYBACK has the correct Journal entries: PAYOUT_REFUND transaction while status is ACTIVE
Given Admin puts EXTERNAL_ASSET_OWNER_TRANSFER job into LOAN_CLOSE_OF_BUSINESS workflow
When Admin sets the business date to "1 May 2023"
@@ -1096,7 +1096,7 @@ Feature: Asset Externalization
| ASSET | 112601 | Loans Receivable | CREDIT | 800.00 |
Then Admin removes EXTERNAL_ASSET_OWNER_TRANSFER job from LOAN_CLOSE_OF_BUSINESS workflow
@AssetExternalizationJournalEntry
@TestRailId:C2757 @AssetExternalizationJournalEntry
Scenario: Verify that Asset externalization SALES and BUYBACK has the correct Journal entries: REPAYMENT_ADJUSTMENT_REFUND chargeback transaction while status is ACTIVE
Given Admin puts EXTERNAL_ASSET_OWNER_TRANSFER job into LOAN_CLOSE_OF_BUSINESS workflow
When Admin sets the business date to "1 May 2023"
@@ -1166,7 +1166,7 @@ Feature: Asset Externalization
| ASSET | 112601 | Loans Receivable | CREDIT | 800.00 |
Then Admin removes EXTERNAL_ASSET_OWNER_TRANSFER job from LOAN_CLOSE_OF_BUSINESS workflow
@AssetExternalizationJournalEntry
@TestRailId:C2758 @AssetExternalizationJournalEntry
Scenario: Verify that Asset externalization SALES and BUYBACK has the correct Journal entries: CHARGE ADJUSTMENT transaction while status is ACTIVE
Given Admin puts EXTERNAL_ASSET_OWNER_TRANSFER job into LOAN_CLOSE_OF_BUSINESS workflow
When Admin sets the business date to "1 May 2023"
@@ -1239,7 +1239,7 @@ Feature: Asset Externalization
| ASSET | 112603 | Interest/Fee Receivable | CREDIT | 200.00 |
Then Admin removes EXTERNAL_ASSET_OWNER_TRANSFER job from LOAN_CLOSE_OF_BUSINESS workflow
@TestRailId:C2759
Scenario: Verify that LoanOwnershipTransferBusinessEvent and LoanAccountSnapshotBusinessEvent is created with correct data
Given Admin puts EXTERNAL_ASSET_OWNER_TRANSFER job into LOAN_CLOSE_OF_BUSINESS workflow
When Admin sets the business date to "1 May 2023"
@@ -1279,7 +1279,7 @@ Feature: Asset Externalization
Then LoanAccountSnapshotBusinessEvent is created
Then Admin removes EXTERNAL_ASSET_OWNER_TRANSFER job from LOAN_CLOSE_OF_BUSINESS workflow
@TestRailId:C2760
Scenario: Verify that LoanOwnershipTransferBusinessEvent and LoanAccountSnapshotBusinessEvent is created with correct data for partial repayment, fee, penalty
Given Admin puts EXTERNAL_ASSET_OWNER_TRANSFER job into LOAN_CLOSE_OF_BUSINESS workflow
When Admin sets the business date to "1 May 2023"
@@ -1322,96 +1322,7 @@ Feature: Asset Externalization
Then LoanAccountSnapshotBusinessEvent is created
Then Admin removes EXTERNAL_ASSET_OWNER_TRANSFER job from LOAN_CLOSE_OF_BUSINESS workflow
# TODO right now COB does not pick up closed loans
@Skip
Scenario: Verify that when loan got fully paid while SALES on PENDING ..........
Given Admin puts EXTERNAL_ASSET_OWNER_TRANSFER job into LOAN_CLOSE_OF_BUSINESS workflow
When Admin sets the business date to "1 May 2023"
When Admin creates a client with random data
When Admin creates a new default Loan with date: "1 May 2023"
And Admin successfully approves the loan on "1 May 2023" with "1000" amount and expected disbursement date on "1 May 2023"
When Admin successfully disburse the loan on "1 May 2023" with "1000" EUR transaction amount
Then Loan status will be "ACTIVE"
When Admin makes asset externalization request by Loan ID with unique ownerExternalId, system-generated transferExternalId and the following data:
| Transaction type | settlementDate | purchasePriceRatio |
| sale | 2023-05-21 | 1 |
Then Asset externalization response has the correct Loan ID, transferExternalId
Then Fetching Asset externalization details by loan id gives numberOfElements: 1 with correct ownerExternalId and the following data:
| settlementDate | purchasePriceRatio | status | effectiveFrom | effectiveTo | Transaction type |
| 2023-05-21 | 1 | PENDING | 2023-05-01 | 9999-12-31 | SALE |
When Admin sets the business date to "10 May 2023"
When Admin runs inline COB job for Loan
And Customer makes "AUTOPAY" repayment on "10 May 2023" with 1000 EUR transaction amount
Then Loan status will be "CLOSED_OBLIGATIONS_MET"
When Admin sets the business date to "22 May 2023"
When Admin runs inline COB job for Loan
# Then Fetching Asset externalization details by loan id gives numberOfElements: 1 with the following data:
# | settlementDate | ownerExternalId | purchasePriceRatio | status | effectiveFrom | effectiveTo |Transaction type |
# | 2023-05-21 | TestOwner | 1 | PENDING | 2023-05-01 | 9999-12-31 |SALE |
Then Admin removes EXTERNAL_ASSET_OWNER_TRANSFER job from LOAN_CLOSE_OF_BUSINESS workflow
# TODO right now COB does not pick up closed loans
@Skip
Scenario: Verify that when loan got overpaid while SALES on PENDING ..........
Given Admin puts EXTERNAL_ASSET_OWNER_TRANSFER job into LOAN_CLOSE_OF_BUSINESS workflow
When Admin sets the business date to "1 May 2023"
When Admin creates a client with random data
When Admin creates a new default Loan with date: "1 May 2023"
And Admin successfully approves the loan on "1 May 2023" with "1000" amount and expected disbursement date on "1 May 2023"
When Admin successfully disburse the loan on "1 May 2023" with "1000" EUR transaction amount
Then Loan status will be "ACTIVE"
When Admin makes asset externalization request by Loan ID with unique ownerExternalId, system-generated transferExternalId and the following data:
| Transaction type | settlementDate | purchasePriceRatio |
| sale | 2023-05-21 | 1 |
Then Asset externalization response has the correct Loan ID, transferExternalId
Then Fetching Asset externalization details by loan id gives numberOfElements: 1 with correct ownerExternalId and the following data:
| settlementDate | purchasePriceRatio | status | effectiveFrom | effectiveTo | Transaction type |
| 2023-05-21 | 1 | PENDING | 2023-05-01 | 9999-12-31 | SALE |
When Admin sets the business date to "10 May 2023"
When Admin runs inline COB job for Loan
And Customer makes "AUTOPAY" repayment on "10 May 2023" with 1200 EUR transaction amount
Then Loan status will be "OVERPAID"
When Admin sets the business date to "22 May 2023"
When Admin runs inline COB job for Loan
# Then Fetching Asset externalization details by loan id gives numberOfElements: 1 with the following data:
# | settlementDate | ownerExternalId | purchasePriceRatio | status | effectiveFrom | effectiveTo |Transaction type |
# | 2023-05-21 | TestOwner | 1 | PENDING | 2023-05-01 | 9999-12-31 |SALE |
Then Admin removes EXTERNAL_ASSET_OWNER_TRANSFER job from LOAN_CLOSE_OF_BUSINESS workflow
# it is for making easier the event check manually on Postman / when event check automation scenarios implemented, it should be deleted
@Skip @events
Scenario: Verify that Asset externalization details are correct after CoB in case of a SALES request by loan id
Given Admin puts EXTERNAL_ASSET_OWNER_TRANSFER job into LOAN_CLOSE_OF_BUSINESS workflow
When Admin sets the business date to "1 May 2023"
When Admin creates a client with random data
When Admin creates a new default Loan with date: "1 May 2023"
And Admin successfully approves the loan on "1 May 2023" with "1000" amount and expected disbursement date on "1 May 2023"
When Admin successfully disburse the loan on "1 May 2023" with "1000" EUR transaction amount
Then Loan status will be "ACTIVE"
When Admin makes asset externalization request by Loan ID with unique ownerExternalId, system-generated transferExternalId and the following data:
| Transaction type | settlementDate | purchasePriceRatio |
| sale | 2023-05-21 | 1 |
Then Asset externalization response has the correct Loan ID, transferExternalId
Then Fetching Asset externalization details by loan id gives numberOfElements: 1 with correct ownerExternalId and the following data:
| settlementDate | purchasePriceRatio | status | effectiveFrom | effectiveTo | Transaction type |
| 2023-05-21 | 1 | PENDING | 2023-05-01 | 9999-12-31 | SALE |
When Admin sets the business date to "22 May 2023"
When Admin runs inline COB job for Loan
Then Fetching Asset externalization details by loan id gives numberOfElements: 2 with correct ownerExternalId and the following data:
| settlementDate | purchasePriceRatio | status | effectiveFrom | effectiveTo | Transaction type |
| 2023-05-21 | 1 | PENDING | 2023-05-01 | 2023-05-21 | SALE |
| 2023-05-21 | 1 | ACTIVE | 2023-05-22 | 9999-12-31 | SALE |
When Admin sets the business date to "25 May 2023"
When Admin runs inline COB job for Loan
When Admin adds "LOAN_SNOOZE_FEE" due date charge with "25 May 2023" due date and 10 EUR transaction amount
When Customer makes "GOODWILL_CREDIT" transaction with "AUTOPAY" payment type on "25 May 2023" with 200 EUR transaction amount and self-generated Idempotency key and check external owner
When Customer makes "PAYOUT_REFUND" transaction with "AUTOPAY" payment type on "25 May 2023" with 200 EUR transaction amount and self-generated Idempotency key and check external owner
When Customer makes "MERCHANT_ISSUED_REFUND" transaction with "AUTOPAY" payment type on "25 May 2023" with 200 EUR transaction amount and self-generated Idempotency key and check external owner
And Customer makes "AUTOPAY" repayment on "25 May 2023" with 200 EUR transaction amount and check external owner
Then Admin removes EXTERNAL_ASSET_OWNER_TRANSFER job from LOAN_CLOSE_OF_BUSINESS workflow
@TestRailId:C2771
Scenario: Verify that SALE and BUYBACK can be cancelled in right order
Given Admin puts EXTERNAL_ASSET_OWNER_TRANSFER job into LOAN_CLOSE_OF_BUSINESS workflow
When Admin sets the business date to "1 May 2023"
@@ -1452,7 +1363,7 @@ Feature: Asset Externalization
| 2023-05-21 | 1 | CANCELLED | 2023-05-01 | 2023-05-10 |
Then Admin removes EXTERNAL_ASSET_OWNER_TRANSFER job from LOAN_CLOSE_OF_BUSINESS workflow
@TestRailId:C2772
Scenario: Verify that SALE can be cancelled
Given Admin puts EXTERNAL_ASSET_OWNER_TRANSFER job into LOAN_CLOSE_OF_BUSINESS workflow
When Admin sets the business date to "1 May 2023"
@@ -1476,7 +1387,7 @@ Feature: Asset Externalization
| 2023-05-21 | 1 | CANCELLED | 2023-05-01 | 2023-05-10 |
Then Admin removes EXTERNAL_ASSET_OWNER_TRANSFER job from LOAN_CLOSE_OF_BUSINESS workflow
@TestRailId:C2773
Scenario: Verify that active SALE can not be cancelled
Given Admin puts EXTERNAL_ASSET_OWNER_TRANSFER job into LOAN_CLOSE_OF_BUSINESS workflow
When Admin sets the business date to "1 May 2023"
@@ -1501,7 +1412,7 @@ Feature: Asset Externalization
When Admin send "cancel" command on "SALE" transaction it will throw an error
Then Admin removes EXTERNAL_ASSET_OWNER_TRANSFER job from LOAN_CLOSE_OF_BUSINESS workflow
@TestRailId:C2774
Scenario: Verify that Asset cannot be cancelled after SALE and BUYBACK is completed
Given Admin puts EXTERNAL_ASSET_OWNER_TRANSFER job into LOAN_CLOSE_OF_BUSINESS workflow
When Admin sets the business date to "1 May 2023"
@@ -1543,7 +1454,7 @@ Feature: Asset Externalization
When Admin send "cancel" command on "SALE" transaction it will throw an error
Then Admin removes EXTERNAL_ASSET_OWNER_TRANSFER job from LOAN_CLOSE_OF_BUSINESS workflow
@TestRailId:C2775
Scenario: Verify that SALE and BUYBACK can be cancelled in right order with double cancel test
Given Admin puts EXTERNAL_ASSET_OWNER_TRANSFER job into LOAN_CLOSE_OF_BUSINESS workflow
When Admin sets the business date to "1 May 2023"
@@ -1604,7 +1515,7 @@ Feature: Asset Externalization
| 2023-05-21 | 1 | CANCELLED | 2023-05-01 | 2023-05-10 |
Then Admin removes EXTERNAL_ASSET_OWNER_TRANSFER job from LOAN_CLOSE_OF_BUSINESS workflow
@TestRailId:C2785
Scenario: Verify that when a loan with PENDING SALES is fully paid asset transfer status will be DECLINED
Given Admin puts EXTERNAL_ASSET_OWNER_TRANSFER job into LOAN_CLOSE_OF_BUSINESS workflow
When Admin sets the business date to "1 May 2023"
@@ -1630,7 +1541,7 @@ Feature: Asset Externalization
Then LoanOwnershipTransferBusinessEvent with transfer status: "DECLINED" and transfer status reason "BALANCE_ZERO" is created
Then Admin removes EXTERNAL_ASSET_OWNER_TRANSFER job from LOAN_CLOSE_OF_BUSINESS workflow
@TestRailId:C2786
Scenario: Verify that when a loan with PENDING SALES is overpaid asset transfer status will be DECLINED
Given Admin puts EXTERNAL_ASSET_OWNER_TRANSFER job into LOAN_CLOSE_OF_BUSINESS workflow
When Admin sets the business date to "1 May 2023"
@@ -1656,7 +1567,7 @@ Feature: Asset Externalization
Then LoanOwnershipTransferBusinessEvent with transfer status: "DECLINED" and transfer status reason "BALANCE_NEGATIVE" is created
Then Admin removes EXTERNAL_ASSET_OWNER_TRANSFER job from LOAN_CLOSE_OF_BUSINESS workflow
@TestRailId:C2787
Scenario: Verify that when a loan with PENDING BUYBACK is fully paid BUYBACK transaction can be done successfully
Given Admin puts EXTERNAL_ASSET_OWNER_TRANSFER job into LOAN_CLOSE_OF_BUSINESS workflow
When Admin sets the business date to "1 May 2023"
@@ -1698,7 +1609,7 @@ Feature: Asset Externalization
| 2023-05-30 | 1 | BUYBACK | 2023-05-22 | 2023-05-25 | BUYBACK |
Then Admin removes EXTERNAL_ASSET_OWNER_TRANSFER job from LOAN_CLOSE_OF_BUSINESS workflow
@TestRailId:C2788
Scenario: Verify that when a loan with PENDING BUYBACK is overpaid BUYBACK transaction can be done successfully
Given Admin puts EXTERNAL_ASSET_OWNER_TRANSFER job into LOAN_CLOSE_OF_BUSINESS workflow
When Admin sets the business date to "1 May 2023"
@@ -1740,7 +1651,7 @@ Feature: Asset Externalization
| 2023-05-30 | 1 | BUYBACK | 2023-05-22 | 2023-05-25 | BUYBACK |
Then Admin removes EXTERNAL_ASSET_OWNER_TRANSFER job from LOAN_CLOSE_OF_BUSINESS workflow
@TestRailId:C2811
Scenario: Verify that transaction and transaction adjustment events has the proper external owner
Given Admin puts EXTERNAL_ASSET_OWNER_TRANSFER job into LOAN_CLOSE_OF_BUSINESS workflow
When Admin sets the business date to "1 May 2023"
@@ -1766,3 +1677,101 @@ Feature: Asset Externalization
And Customer makes "AUTOPAY" repayment on "22 May 2023" with 10 EUR transaction amount and check external owner
When Customer adjust "1"th repayment on "22 May 2023" with amount "9" and check external owner
Then Admin removes EXTERNAL_ASSET_OWNER_TRANSFER job from LOAN_CLOSE_OF_BUSINESS workflow
@TestRailId:C3193
Scenario: Verify that Asset externalization SALES and BUYBACK has the correct Journal entries: no other transactions - interest bearing loan
Given Admin puts EXTERNAL_ASSET_OWNER_TRANSFER job into LOAN_CLOSE_OF_BUSINESS workflow
When Admin sets the business date to "1 May 2023"
When Admin creates a client with random data
When Admin creates a fully customized loan with the following data:
| LoanProduct | submitted on date | with Principal | ANNUAL interest rate % | interest type | interest calculation period | amortization type | loanTermFrequency | loanTermFrequencyType | repaymentEvery | repaymentFrequencyType | numberOfRepayments | graceOnPrincipalPayment | graceOnInterestPayment | interest free period | Payment strategy |
| LP2_ADV_PYMNT_INTEREST_DAILY_EMI_ACTUAL_ACTUAL | 01 May 2023 | 1000 | 12 | DECLINING_BALANCE | DAILY | EQUAL_INSTALLMENTS | 6 | MONTHS | 1 | MONTHS | 6 | 0 | 0 | 0 | ADVANCED_PAYMENT_ALLOCATION |
And Admin successfully approves the loan on "1 May 2023" with "1000" amount and expected disbursement date on "1 May 2023"
When Admin successfully disburse the loan on "1 May 2023" with "1000" EUR transaction amount
Then Loan status will be "ACTIVE"
When Admin makes asset externalization request by Loan ID with unique ownerExternalId, system-generated transferExternalId and the following data:
| Transaction type | settlementDate | purchasePriceRatio |
| sale | 2023-05-21 | 1 |
Then Asset externalization response has the correct Loan ID, transferExternalId
Then Fetching Asset externalization details by loan id gives numberOfElements: 1 with correct ownerExternalId and the following data:
| settlementDate | purchasePriceRatio | status | effectiveFrom | effectiveTo | Transaction type |
| 2023-05-21 | 1 | PENDING | 2023-05-01 | 9999-12-31 | SALE |
When Admin adds "LOAN_SNOOZE_FEE" due date charge with "10 May 2023" due date and 10 EUR transaction amount
When Admin sets the business date to "10 May 2023"
When Admin runs inline COB job for Loan
When Admin sets the business date to "22 May 2023"
When Admin runs inline COB job for Loan
Then LoanOwnershipTransferBusinessEvent is created
Then LoanAccountSnapshotBusinessEvent is created
Then Fetching Asset externalization details by loan id gives numberOfElements: 2 with correct ownerExternalId and the following data:
| settlementDate | purchasePriceRatio | status | effectiveFrom | effectiveTo | Transaction type |
| 2023-05-21 | 1 | PENDING | 2023-05-01 | 2023-05-21 | SALE |
| 2023-05-21 | 1 | ACTIVE | 2023-05-22 | 9999-12-31 | SALE |
Then The latest asset externalization transaction with "ACTIVE" status has the following TRANSFER Journal entries:
| glAccountType | glAccountCode | glAccountName | entryType | amount |
| ASSET | 112601 | Loans Receivable | CREDIT | 1000.00 |
| ASSET | 112603 | Interest/Fee Receivable | CREDIT | 45.57 |
| ASSET | 146000 | Asset transfer | DEBIT | 1045.57 |
| ASSET | 112601 | Loans Receivable | DEBIT | 1000.00 |
| ASSET | 112603 | Interest/Fee Receivable | DEBIT | 45.57 |
| ASSET | 146000 | Asset transfer | CREDIT | 1045.57 |
Then The asset external owner has the following OWNER Journal entries:
| glAccountType | glAccountCode | glAccountName | entryType | amount |
| ASSET | 112601 | Loans Receivable | DEBIT | 1000.00 |
| ASSET | 112603 | Interest/Fee Receivable | DEBIT | 45.57 |
When Admin makes asset externalization request by Loan ID with unique ownerExternalId, system-generated transferExternalId and the following data:
| Transaction type | settlementDate | purchasePriceRatio |
| buyback | 2023-05-30 | |
Then Fetching Asset externalization details by loan id gives numberOfElements: 3 with correct ownerExternalId and the following data:
| settlementDate | purchasePriceRatio | status | effectiveFrom | effectiveTo | Transaction type |
| 2023-05-21 | 1 | PENDING | 2023-05-01 | 2023-05-21 | SALE |
| 2023-05-21 | 1 | ACTIVE | 2023-05-22 | 9999-12-31 | SALE |
| 2023-05-30 | 1 | BUYBACK | 2023-05-22 | 9999-12-31 | BUYBACK |
When Admin adds "LOAN_NSF_FEE" due date charge with "25 May 2023" due date and 20 EUR transaction amount
When Admin sets the business date to "26 May 2023"
When Admin runs inline COB job for Loan
When Admin sets the business date to "31 May 2023"
When Admin runs inline COB job for Loan
Then LoanOwnershipTransferBusinessEvent is created
Then LoanAccountSnapshotBusinessEvent is created
Then Fetching Asset externalization details by loan id gives numberOfElements: 3 with correct ownerExternalId and the following data:
| settlementDate | purchasePriceRatio | status | effectiveFrom | effectiveTo | Transaction type |
| 2023-05-21 | 1 | PENDING | 2023-05-01 | 2023-05-21 | SALE |
| 2023-05-21 | 1 | ACTIVE | 2023-05-22 | 2023-05-30 | SALE |
| 2023-05-30 | 1 | BUYBACK | 2023-05-22 | 2023-05-30 | BUYBACK |
Then The latest asset externalization transaction with "BUYBACK" status has the following TRANSFER Journal entries:
| glAccountType | glAccountCode | glAccountName | entryType | amount |
| ASSET | 112601 | Loans Receivable | DEBIT | 1000.00 |
| ASSET | 112603 | Interest/Fee Receivable | DEBIT | 65.57 |
| ASSET | 146000 | Asset transfer | CREDIT | 1065.57 |
| ASSET | 112601 | Loans Receivable | CREDIT | 1000.00 |
| ASSET | 112603 | Interest/Fee Receivable | CREDIT | 65.57 |
| ASSET | 146000 | Asset transfer | DEBIT | 1065.57 |
Then The asset external owner has the following OWNER Journal entries:
| glAccountType | glAccountCode | glAccountName | entryType | amount |
| ASSET | 112601 | Loans Receivable | DEBIT | 1000.00 |
| ASSET | 112603 | Interest/Fee Receivable | DEBIT | 45.57 |
| ASSET | 112603 | Interest/Fee Receivable | DEBIT | 0.33 |
| INCOME | 404000 | Interest Income | CREDIT | 0.33 |
| ASSET | 112603 | Interest/Fee Receivable | DEBIT | 0.33 |
| INCOME | 404000 | Interest Income | CREDIT | 0.33 |
| ASSET | 112603 | Interest/Fee Receivable | DEBIT | 0.33 |
| INCOME | 404000 | Interest Income | CREDIT | 0.33 |
| ASSET | 112603 | Interest/Fee Receivable | DEBIT | 0.33 |
| INCOME | 404000 | Interest Income | CREDIT | 0.33 |
| ASSET | 112603 | Interest/Fee Receivable | DEBIT | 0.33 |
| INCOME | 404000 | Interest Income | CREDIT | 0.33 |
| ASSET | 112603 | Interest/Fee Receivable | DEBIT | 0.33 |
| INCOME | 404000 | Interest Income | CREDIT | 0.33 |
| ASSET | 112603 | Interest/Fee Receivable | DEBIT | 0.33 |
| INCOME | 404000 | Interest Income | CREDIT | 0.33 |
| ASSET | 112603 | Interest/Fee Receivable | DEBIT | 0.33 |
| INCOME | 404000 | Interest Income | CREDIT | 0.33 |
| ASSET | 112603 | Interest/Fee Receivable | DEBIT | 0.33 |
| INCOME | 404000 | Interest Income | CREDIT | 0.33 |
| ASSET | 112603 | Interest/Fee Receivable | DEBIT | 0.33 |
| INCOME | 404000 | Interest Income | CREDIT | 0.33 |
| ASSET | 112603 | Interest/Fee Receivable | DEBIT | 0.33 |
| INCOME | 404000 | Interest Income | CREDIT | 0.33 |
Then Admin removes EXTERNAL_ASSET_OWNER_TRANSFER job from LOAN_CLOSE_OF_BUSINESS workflow
fineract-e2e-tests-runner/src/test/resources/features/BatchApi.feature
+10 -10
View File
@@ -1,12 +1,12 @@
@BatchApiFeature
Feature: Batch API
@TestRailId:C63
Scenario: As a user I would like to run a sample Batch API scenario
When Batch API sample call ran
Then Admin checks that all steps result 200OK
@idempotency
@TestRailId:C2484 @idempotency
Scenario: As admin I would like to verify that idempotency applies correctly in case of BatchAPI call with the same idempotency key on two repayments
When Batch API call runs with idempotency key
Then Admin checks that all steps result 200OK for Batch API idempotency request
@@ -16,24 +16,24 @@ Feature: Batch API
Then Batch API response has the same idempotency key in segment with requestId 6 as in segment with requestId 5
Then Loan has 1 "REPAYMENT" transactions on Transactions tab after Batch API run
@TestRailId:C2640
Scenario: Verify Batch API call in case of enclosing transaction is TRUE and all steps result 200OK
When Batch API call with steps: createClient, createLoan, approveLoan, getLoanDetails runs with enclosingTransaction: "true"
Then Admin checks that all steps result 200OK
@TestRailId:C2641
Scenario: Verify Batch API call in case of enclosing transaction is TRUE and one of the steps fails
When Batch API call with steps: createClient, createLoan, approveLoan, getLoanDetails runs with enclosingTransaction: "true", with failed approve step
Then Verify that step 3 throws an error with error code 404
Then Nr. 1 Client creation was rolled back
Then Nr. 1 Loan creation was rolled back
@TestRailId:C2642
Scenario: Verify Batch API call in case of enclosing transaction is FALSE and all steps result 200OK
When Batch API call with steps: createClient, createLoan, approveLoan, getLoanDetails runs with enclosingTransaction: "false"
Then Admin checks that all steps result 200OK
@TestRailId:C2643
Scenario: Verify Batch API call in case of enclosing transaction is FALSE, there is only one reference-tree and one of the steps fails
When Batch API call with steps: createClient, createLoan, approveLoan, getLoanDetails runs with enclosingTransaction: "false", with failed approve step
Then Verify that step Nr. 1 results 200
@@ -43,12 +43,12 @@ Feature: Batch API
Then Nr. 1 Client was created
Then Nr. 1 Loan was created
@TestRailId:C2644
Scenario: Verify Batch API call in case of enclosing transaction is FALSE, there are two reference-trees and all steps result 200
When Batch API call with steps done twice: createClient, createLoan, approveLoan, getLoanDetails runs with enclosingTransaction: "false"
Then Admin checks that all steps result 200OK
@TestRailId:C2645
Scenario: Verify Batch API call in case of enclosing transaction is FALSE, there are two reference-trees and one of the steps in second tree fails
When Batch API call with steps done twice: createClient, createLoan, approveLoan, getLoanDetails runs with enclosingTransaction: "false", with failed approve step in second tree
Then Verify that step Nr. 1 results 200
@@ -65,14 +65,14 @@ Feature: Batch API
Then Nr. 2 Client was created
Then Nr. 2 Loan was created
@TestRailId:C2646
Scenario: Verify Batch API call in case of enclosing transaction is FALSE and one of the steps is doubled
When Batch API call with steps: createClient, createLoan, approveLoan, getLoanDetails runs with enclosingTransaction: "false", and approveLoan is doubled
Then Admin checks that all steps result 200OK
Then Batch API response has no "x-served-from-cache" field in segment with requestId 3
Then Batch API response has boolean value in header "x-served-from-cache": "true" in segment with requestId 4
@TestRailId:C2840
Scenario: Verify datatable Batch API calls, when the second request relies on the first response, but the first response is empty
When A datatable for "Loan" is created
And Batch API call with steps: queryDatatable, updateDatatable runs, with empty queryDatatable response
fineract-e2e-tests-runner/src/test/resources/features/BusinessDate.feature
+5 -5
View File
@@ -1,27 +1,27 @@
@BusinessDateFeature
Feature: BusinessDate
@TestRailId:C38
Scenario: As a user I would like to enable the Business date configuration
Given Global configuration "enable-business-date" is enabled
@TestRailId:C39
Scenario: As a user I would like to disable the Business date configuration
Given Global configuration "enable-business-date" is disabled
@TestRailId:C40
Scenario: As a user I would like to set the business date
When Admin sets the business date to "10 July 2022"
Then Admin checks that the business date is correctly set to "10 July 2022"
@TestRailId:C41
Scenario: As a user I would like to change the business date manually
When Admin sets the business date to "10 July 2022"
Then Admin checks that the business date is correctly set to "10 July 2022"
When Admin sets the business date to "11 July 2022"
Then Admin checks that the business date is correctly set to "11 July 2022"
@TestRailId:C27
Scenario: As a user I would like to change the business date with scheduled job
When Admin sets the business date to "10 July 2022"
When Admin runs the Increase Business Date by 1 day job
fineract-e2e-tests-runner/src/test/resources/features/Client.feature
+2 -20
View File
@@ -1,26 +1,7 @@
#
# Licensed to the Apache Software Foundation (ASF) under one
# or more contributor license agreements. See the NOTICE file
# distributed with this work for additional information
# regarding copyright ownership. The ASF licenses this file
# to you under the Apache License, Version 2.0 (the
# "License"); you may not use this file except in compliance
# with the License. You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing,
# software distributed under the License is distributed on an
# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
# KIND, either express or implied. See the License for the
# specific language governing permissions and limitations
# under the License.
#
@ClientFeature
Feature: Client
@Smoke
@TestRailId:C14 @Smoke
Scenario Outline: Client creation functionality for Fineract
When Admin creates a client with Firstname <firstName> and Lastname <lastName>
Then Client is created successfully
@@ -29,6 +10,7 @@ Feature: Client
| "FirstName1" | "Test1" |
@TestRailId:C15
Scenario Outline: Client creation with address functionality for Fineract
When Global configuration "enable-address" is enabled
When Admin creates a client with Firstname <firstName> and Lastname <lastName> with address
fineract-e2e-tests-runner/src/test/resources/features/InlineCOB.feature
+7 -7
View File
@@ -1,7 +1,7 @@
@InlineCOBFeature
Feature: InlineCOBFeature
@TestRailId:C2457
Scenario: As an admin I would like to see that inline COB Happy Path scenario is working properly
When Admin sets the business date to "1 January 2022"
When Admin creates a client with random data
@@ -12,7 +12,7 @@ Feature: InlineCOBFeature
When Admin runs inline COB job for Loan
Then Admin checks that delinquency range is: "RANGE_3" and has delinquentDate "2022-02-03"
@TestRailId:C2473
Scenario: As an admin I would like to see that loan was catching up with inline COB
When Admin sets the business date to "1 January 2022"
When Admin creates a client with random data
@@ -27,7 +27,7 @@ Feature: InlineCOBFeature
When Admin runs inline COB job for Loan
Then Admin checks that last closed business date of loan is "04 January 2022"
@TestRailId:C2554
Scenario: As an admin I would like to see that loan was catching up with inline COB on a repayment
When Admin sets the business date to "1 January 2022"
When Admin creates a client with random data
@@ -44,7 +44,7 @@ Feature: InlineCOBFeature
And Created user makes "AUTOPAY" repayment on "5 January 2022" with 100 EUR transaction amount
Then Admin checks that last closed business date of loan is "04 January 2022"
@TestRailId:C2602
Scenario: Verify that LoanCOBApiFilter works fine in the background and loanId controlled transaction does not trigger inlineCOB if COB had not been applied on loan before
When Admin sets the business date to "01 January 2023"
When Admin creates a client with random data
@@ -67,7 +67,7 @@ Feature: InlineCOBFeature
| RANGE_1 | 06 January 2023 | 07 January 2023 |
Then Admin checks that last closed business date of loan is "null"
@TestRailId:C2603
Scenario: Verify that LoanCOBApiFilter works fine in the background and externalId controlled transaction does not trigger inlineCOB if COB had not been applied on loan before
When Admin sets the business date to "01 January 2023"
When Admin creates a client with random data
@@ -90,7 +90,7 @@ Feature: InlineCOBFeature
| RANGE_1 | 06 January 2023 | 07 January 2023 |
Then Admin checks that last closed business date of loan is "null"
@TestRailId:C2604
Scenario: Verify that LoanCOBApiFilter works fine in the background and loanId controlled transaction triggers inlineCOB if COB had been applied on loan before
When Admin sets the business date to "01 January 2023"
When Admin creates a client with random data
@@ -116,7 +116,7 @@ Feature: InlineCOBFeature
| RANGE_1 | 06 January 2023 | 07 January 2023 |
Then Admin checks that last closed business date of loan is "06 January 2023"
@TestRailId:C2605
Scenario: Verify that LoanCOBApiFilter works fine in the background and externalId controlled transaction triggers inlineCOB if COB had been applied on loan before
When Admin sets the business date to "01 January 2023"
When Admin creates a client with random data