You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@fineract.apache.org by "Myrle Krantz (JIRA)" <ji...@apache.org> on 2018/10/11 18:19:00 UTC

[jira] [Assigned] (FINCN-22) Fix TestSuite in teller

     [ https://issues.apache.org/jira/browse/FINCN-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Myrle Krantz reassigned FINCN-22:
---------------------------------

    Assignee: cabrel kemfang

> Fix TestSuite in teller
> -----------------------
>
>                 Key: FINCN-22
>                 URL: https://issues.apache.org/jira/browse/FINCN-22
>             Project: Fineract Cloud Native
>          Issue Type: Bug
>          Components: fineract-cn-teller
>            Reporter: Myrle Krantz
>            Assignee: cabrel kemfang
>            Priority: Major
>
> As a programmer I want to be able to find out quickly if my changes have caused existing functionality to break.  The TestSuite class in the component-test module of the fineract cn services is there to make one-click testing of the services easy.
> Currently when the TestSuite of fineract-cn-teller is run, only the first Test class passes.  The following test fails, and the remaining tests aren't even included in the suite.  These test pass when they are run individually however.  Apparently some part of the service spin up which should be part of the base class is still in the child classes.  This causes spin-up to fail because the spin down is not completed by the time the next class starts.
> Once this is fixed, you should also add the two missing test classes to the test suite.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)