LeeYoonMyeong created FINERACT-2989:
---------------------------------------
Summary: Flaky E2E: Working Capital adjust-by-delta UC40 status
changed event check sometimes sees status 600 instead of 300
Key: FINERACT-2989
URL: https://issues.apache.org/jira/browse/FINERACT-2989
Project: Apache Fineract
Issue Type: Bug
Components: Savings
Reporter: LeeYoonMyeong
The E2E scenario "Verify Working Capital Loan adjust by delta transaction -
UC40: full decrease of closing repayment re-opens loan and raises status
changed event" ({{WorkingCapitalLoanAdjustByDelta-Adjust.feature}}, added in
FINERACT-2455) fails intermittently in the step "a Working Capital Loan Status
Changed business event is raised":
{noformat}
org.opentest4j.AssertionFailedError: [status.id]
expected: 300L
but was: 600L
at
org.apache.fineract.test.messaging.event.EventCheckHelper.assertWorkingCapitalLoanAccountData(EventCheckHelper.java:1578)
at
org.apache.fineract.test.messaging.event.EventCheckHelper.workingCapitalLoanStatusChangedEventCheck(EventCheckHelper.java:812)
{noformat}
Observed results for the same scenario:
* develop at ad98847: failed -
https://github.com/apache/fineract/actions/runs/40026935216/job/120669893735
* develop at 4c9ec8d: passed -
https://github.com/apache/fineract/actions/runs/40090963619/job/120865834646
* PR #6731 (based on 4c9ec8d, only changes TaxUtils): failed -
https://github.com/apache/fineract/actions/runs/40092299403/job/120868874199
In this scenario the loan is first closed (status 600, CLOSED_OBLIGATIONS_MET)
and then re-opened (status 300, ACTIVE), so two Status Changed events are
raised for the same loan. The check may be matching the earlier event depending
on timing (not verified).
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
