[#FINERACT-2422] standardize use of aging vs. ageing (#5289)

This commit is contained in:
Kengne-yvana
2026-01-08 10:43:21 -06:00
committed by GitHub
parent 4c1016d239
commit 61034e6041
71 changed files with 321 additions and 321 deletions
@@ -2146,7 +2146,7 @@ Feature: LoanDelinquency
| 5 | RANGE_90 | 250.00 |
@TestRailId:C4140
Scenario: Verify that loan delinquent days are correct when graceOnArrearsAgeing is set on loan product level (value=3)
Scenario: Verify that loan delinquent days are correct when graceOnArrearsAging is set on loan product level (value=3)
When Admin sets the business date to "01 January 2025"
And Admin creates a client with random data
And Admin creates a fully customized loan with the following data:
@@ -2162,11 +2162,11 @@ Feature: LoanDelinquency
| RANGE_90 | 666.68 | 04 February 2025 | 100 | 103 |
@TestRailId:C4141
Scenario: Verify that loan delinquent days are correct when graceOnArrearsAgeing is overrided on loan level (value=5)
Scenario: Verify that loan delinquent days are correct when graceOnArrearsAging is overrided on loan level (value=5)
When Admin sets the business date to "01 January 2025"
And Admin creates a client with random data
And Admin creates a fully customized loan with graceOnArrearsAgeing and 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 | graceOnArrearsAgeing |
And Admin creates a fully customized loan with graceOnArrearsAging and 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 | graceOnArrearsAging |
| LP2_PROGRESSIVE_ADVANCED_PAYMENT_ALLOCATION_BUYDOWN_FEES | 01 January 2025 | 1000 | 0 | DECLINING_BALANCE | DAILY | EQUAL_INSTALLMENTS | 6 | MONTHS | 1 | MONTHS | 6 | 0 | 0 | 0 | ADVANCED_PAYMENT_ALLOCATION | 5 |
And Admin successfully approves the loan on "01 January 2025" with "1000" amount and expected disbursement date on "01 January 2025"
And Admin successfully disburse the loan on "01 January 2025" with "1000" EUR transaction amount
@@ -10,11 +10,11 @@ Feature: LoanOverrideFields
| inArrearsTolerance | null |
| graceOnPrincipalPayment | null |
| graceOnInterestPayment | null |
| graceOnArrearsAgeing | null |
| graceOnArrearsAging | null |
Then LoanDetails has "inArrearsTolerance" field with value: "10"
Then LoanDetails has "graceOnPrincipalPayment" field with value: "1"
Then LoanDetails has "graceOnInterestPayment" field with value: "1"
Then LoanDetails has "graceOnArrearsAgeing" field with value: "3"
Then LoanDetails has "graceOnArrearsAging" field with value: "3"
@TestRailId:C4143
Scenario: Verify that all nullable fields ignore overrides when overrides not allowed
@@ -25,11 +25,11 @@ Feature: LoanOverrideFields
| inArrearsTolerance | 11 |
| graceOnPrincipalPayment | 2 |
| graceOnInterestPayment | 2 |
| graceOnArrearsAgeing | 4 |
| graceOnArrearsAging | 4 |
Then LoanDetails has "inArrearsTolerance" field with value: "10"
Then LoanDetails has "graceOnPrincipalPayment" field with value: "1"
Then LoanDetails has "graceOnInterestPayment" field with value: "1"
Then LoanDetails has "graceOnArrearsAgeing" field with value: "3"
Then LoanDetails has "graceOnArrearsAging" field with value: "3"
@TestRailId:C4144
Scenario: Verify that nullable fields default to product when override is allowed but not provided
@@ -40,11 +40,11 @@ Feature: LoanOverrideFields
| inArrearsTolerance | null |
| graceOnPrincipalPayment | null |
| graceOnInterestPayment | null |
| graceOnArrearsAgeing | null |
| graceOnArrearsAging | null |
Then LoanDetails has "inArrearsTolerance" field with value: "10"
Then LoanDetails has "graceOnPrincipalPayment" field with value: "1"
Then LoanDetails has "graceOnInterestPayment" field with value: "1"
Then LoanDetails has "graceOnArrearsAgeing" field with value: "3"
Then LoanDetails has "graceOnArrearsAging" field with value: "3"
@TestRailId:C4145
Scenario: Verify that nullable fields default to product when override is allowed and provided
@@ -55,8 +55,8 @@ Feature: LoanOverrideFields
| inArrearsTolerance | 11 |
| graceOnPrincipalPayment | 2 |
| graceOnInterestPayment | 2 |
| graceOnArrearsAgeing | 4 |
| graceOnArrearsAging | 4 |
Then LoanDetails has "inArrearsTolerance" field with value: "11"
Then LoanDetails has "graceOnPrincipalPayment" field with value: "2"
Then LoanDetails has "graceOnInterestPayment" field with value: "2"
Then LoanDetails has "graceOnArrearsAgeing" field with value: "4"
Then LoanDetails has "graceOnArrearsAging" field with value: "4"
@@ -518,7 +518,7 @@ Feature: LoanReAging
Then Loan is closed with zero outstanding balance and it's all installments have obligations met
@TestRailId:C3059 @AdvancedPaymentAllocation
Scenario: Verify Loan re-aging transaction - partial principal payment scenario + undo re-ageing
Scenario: Verify Loan re-aging transaction - partial principal payment scenario + undo re-aging
When Admin sets the business date to "01 January 2024"
When Admin creates a client with random data
When Admin set "LP2_DOWNPAYMENT_AUTO_ADVANCED_PAYMENT_ALLOCATION" loan product "DEFAULT" transaction type to "NEXT_INSTALLMENT" future installment allocation rule