Michael Vorburger created FINERACT-1244:
-------------------------------------------
Summary: ClientLoanIntegrationTest >
checkClientLoanCreateAndDisburseFlow() FAILED Expected status code <200> but
was <403>
Key: FINERACT-1244
URL: https://issues.apache.org/jira/browse/FINERACT-1244
Project: Apache Fineract
Issue Type: Bug
Reporter: Michael Vorburger
https://travis-ci.org/github/apache/fineract/builds/739089394 for
https://github.com/apache/fineract/pull/1465 failed with:
{noformat}> Task :integration-tests:test
ClientLoanIntegrationTest > checkClientLoanCreateAndDisburseFlow() FAILED
java.lang.AssertionError: 1 expectation failed.
Expected status code <200> but was <403>.
(...)
at
org.apache.fineract.integrationtests.common.Utils.performServerPost(Utils.java:159)
at
org.apache.fineract.integrationtests.common.loans.LoanTransactionHelper.getLoanProductId(LoanTransactionHelper.java:78)
at
org.apache.fineract.integrationtests.ClientLoanIntegrationTest.createLoanProduct(ClientLoanIntegrationTest.java:905)
at
org.apache.fineract.integrationtests.ClientLoanIntegrationTest.checkClientLoanCreateAndDisburseFlow(ClientLoanIntegrationTest.java:109)
ClientLoanIntegrationTest >
testLoanScheduleWithInterestRecalculation_WITH_ORIGINAL_REPAYMENT_BASED_ARREARS_AGEING()
SKIPPED{noformat}
This reminds me of FINERACT-885.. do we perhaps still (again) have a new _date
issue that breaks the integration test on the last couple of days every month_?
Or could this somehow be related to an impact of
https://github.com/apache/fineract/pull/1179 for FINERACT-826? Just a.. hunch.
NB _Expected status code <200> but was <403>_, where HTTP 403 =
https://en.wikipedia.org/wiki/HTTP_403 would be a Permission / Authorization
issue, not a failed data validation (if it's accurate; but it's well possible
Fineract sends inappropriate HTTP response codes, of course).
[~ptuomola] any other thoughts?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
