[ 
https://issues.apache.org/jira/browse/FINERACT-1293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17266348#comment-17266348
 ] 

Michael Vorburger commented on FINERACT-1293:
---------------------------------------------

> that _"perhaps these individual test methods are not as isolated from each 
> other as they should be"_.

I wondered if this perhaps had something to do with 
[https://junit.org/junit5/docs/current/user-guide/#writing-tests-test-execution-order],
 and tried adding {{@TestMethodOrder(MethodName.class)}}, but that didn't seem 
to help. (I've still raised https://github.com/apache/fineract/pull/1577 to add 
that, just to avoid future confusion about this.)

> something to do with the export {{TZ=Asia/Kolkata}} in 
> https://github.com/apache/fineract/blob/develop/.travis.yml#L55 ?

Running the {{SchedulerJobsTestResults}} by adding {{TZ=Asia/Kolkata}} (in 
Eclipse, where I'm facing this problem) doesn't help here either.

I'm hitting this when running the test locally in Eclipse; perhaps running just 
this test locally from Gradle makes a difference?

Otherwise it may be that it somehow relies on a previously run other test.

> SchedulerJobsTestResults testInterestTransferForSavings() and 
> testExecuteStandingInstructionsJobOutcome() fail when run locally, but pass 
> on Travis CI
> ------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: FINERACT-1293
>                 URL: https://issues.apache.org/jira/browse/FINERACT-1293
>             Project: Apache Fineract
>          Issue Type: Bug
>            Reporter: Michael Vorburger
>            Priority: Major
>
> While locally investigating FINERACT-924, I've found that the problem from 
> that issue (the testApplyAnnualFeeForSavingsJobOutcome()) WORKED locally for 
> me, but instead 2 other tests locally consistently failed on me, even though 
> they do seem to always pass on Travis CI, namely:
> {noformat}
> org.opentest4j.AssertionFailedError: Verifying opening Balance ==> expected: 
> <100000.0> but was: <100918.32>
>       at 
> org.apache.fineract.integrationtests.SchedulerJobsTestResults.testInterestTransferForSavings(SchedulerJobsTestResults.java:897){noformat}
> and:
> {noformat}
> org.opentest4j.AssertionFailedError: Verifying From Savings Balance after 
> Successful completion of Scheduler Job ==> expected: <500.0> but was: <1000.0>
>       at 
> org.apache.fineract.integrationtests.SchedulerJobsTestResults.testExecuteStandingInstructionsJobOutcome(SchedulerJobsTestResults.java:659){noformat}
> This already came up back in FINERACT-857, where I had suspected that 
> _"perhaps these individual test methods are not as isolated from each other 
> as they should be"_.
> Or maybe that has something to do with the {{export TZ=Asia/Kolkata}} in 
> [https://github.com/apache/fineract/blob/develop/.travis.yml#L55] ?
> [~ptuomola] (or perhaps [~aleks]) I don't suppose you happen to know more 
> about this?



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

Reply via email to