Details
-
Sub-task
-
Status: Resolved
-
Blocker
-
Resolution: Fixed
-
None
-
None
-
None
Description
See comments in FINERACT-855 from yesterday and today re. testPrematureClosureAmountWithPenalInterestTillPrematureWithdrawal_With_360_Days():
org.apache.fineract.integrationtests.RecurringDepositTest > testPrematureClosureAmountWithPenalInterestTillPrematureWithdrawal_With_360_Days FAILED java.lang.AssertionError: Verifying Pre-Closure maturity amount expected:<4005.0> but was:<4006.0> at org.junit.Assert.fail(Assert.java:89) at org.junit.Assert.failNotEquals(Assert.java:835) at org.junit.Assert.assertEquals(Assert.java:120) at org.apache.fineract.integrationtests.RecurringDepositTest.testPrematureClosureAmountWithPenalInterestTillPrematureWithdrawal_With_360_Days(RecurringDepositTest.java:2161)
Because this problem probably actually has nothing at all to do with the testRecurringDepositAccountWithClosureTypeTransferToSavings_WITH_HOLD_TAX() failure which FINERACT-855 was originally about, so let's track this separately here.
This testPrematureClosureAmountWithPenalInterestTillPrematureWithdrawal_With_360_Days() failure today seems to have nothing to do with the Job Scheduler (for once), but appears to be some date related mess.
That test today right for me reliably fails locally, but when I change my system date back a few days to late May, then it passes. So either the test, or worse even the actual logic being tested, has some bug in date handling.
Attachments
Issue Links
- is related to
-
FINERACT-1069 RecurringDepositTest / FixedDepositTests failing on 1st of month
- Closed
- links to