Michael Vorburger created FINERACT-1248:
-------------------------------------------

             Summary: RecurringDepositTest > 
testRecurringDepositAccountWithClosureTypeTransferToSavings_WITH_HOLD_TAX: 
Journal Entry not found ==> expected: <true> but was: <false
                 Key: FINERACT-1248
                 URL: https://issues.apache.org/jira/browse/FINERACT-1248
             Project: Apache Fineract
          Issue Type: Bug
            Reporter: Michael Vorburger


https://travis-ci.org/github/apache/fineract/builds/740417097 for 
https://github.com/apache/fineract/pull/1474 (related to FINERACT-1241 and 
FINERACT-1247) failed with:

{noformat}RecurringDepositTest > 
testRecurringDepositAccountWithClosureTypeTransferToSavings_WITH_HOLD_TAX() 
FAILED

    org.opentest4j.AssertionFailedError: Journal Entry not found ==> expected: 
<true> but was: <false>

        at org.junit.jupiter.api.AssertionUtils.fail(AssertionUtils.java:55)

        at org.junit.jupiter.api.AssertTrue.assertTrue(AssertTrue.java:40)

        at org.junit.jupiter.api.Assertions.assertTrue(Assertions.java:193)

        at 
org.apache.fineract.integrationtests.common.accounting.JournalEntryHelper.checkJournalEntry(JournalEntryHelper.java:82)

        at 
org.apache.fineract.integrationtests.common.accounting.JournalEntryHelper.checkJournalEntryForLiabilityAccount(JournalEntryHelper.java:55)

        at 
org.apache.fineract.integrationtests.RecurringDepositTest.testRecurringDepositAccountWithClosureTypeTransferToSavings_WITH_HOLD_TAX(RecurringDepositTest.java:836){noformat}

This looks a bit like past FINERACT-855 or FINERACT-1016 where [~ptuomola] was 
able to do magic to fix.

As I'd like to unblock the completely broken {{develop}} branch, I won't 
investigate details here, but just add an {{@Ignore}} for this test as part of 
https://github.com/apache/fineract/pull/1474, and hope that someone else is 
motivated to fix this Blocker.

PS: Perhaps this is one of our date problems? It's Oct 31st today - last day of 
the month...



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to