[
https://issues.apache.org/jira/browse/FINERACT-827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17013812#comment-17013812
]
Michael Vorburger commented on FINERACT-827:
--------------------------------------------
> What's super confusing
I sank some more time into this, and can't figure out what's going on with this
integration test... just to be sure that there are no "side effects", I ran:
{{./gradlew clean && ./gradlew dropDB -PdbName=mifostenant-default && ./gradlew
createDB -PdbName=mifostenant-default && ./gradlew integrationTest}}
saw it fail in
{{./build/test-results/integrationTest/TEST-org.apache.fineract.integrationtests.common.shares.ShareAccountIntegrationTests.xml}}
with {{ComparisonFailure: amountOutstanding expected:<[0].0>; but
was:<[2].0>}},
fixed that (so changed expected amountOutstanding from 0.0 to 2.0), and ran it
again (with clean & dropDB, just to be extra sure!),
it failed again, note it's now amountPaid (not amountOutstanding) with:
ComparisonFailure: amountPaid expected:<[2.]0> but was:<[]0>}}
fixed that as well (so changed expected amountPaid from 2.0 to 0), and ran it
again (again with clean & dropDB),
it failed again, now with ComparisonFailure: amountOutstanding expected:<[2].0>
but was:<[0].0>, which is going around in circles?!
Something is really broken somewhere related to this code.
> ShareAccountCharge is missing hashCode() & equals() but adding it fails
> ShareAccountIntegrationTests
> ----------------------------------------------------------------------------------------------------
>
> Key: FINERACT-827
> URL: https://issues.apache.org/jira/browse/FINERACT-827
> Project: Apache Fineract
> Issue Type: Bug
> Reporter: Michael Vorburger
> Priority: Blocker
>
> During work in FINERACT-702 (specifically during
> [pull/684|https://github.com/apache/fineract/pull/684]), we've stumbled upon
> {{ShareAccountCharge}} missing required {{hashCode()}} & {{equals()}}
> methods, but found that adding them fails the
> {{ShareAccountIntegrationTests}}.
> This is likely an indication of a major bug worth further investigating.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
