[jira] [Updated] (FINERACT-713) Improve code-coverage to at-least 50% and reduce execution time
[ https://issues.apache.org/jira/browse/FINERACT-713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishwas Babu A J updated FINERACT-713: -- Description: While Fineract has integration tests, they currently cover very limited scenarios and code coverage is very low. Enable gradle plugins to report the current code coverage and add new Integration tests to ensure that code coverage, esp in critical packages like loans, savings, and accounting is at-least 50%. Once the packages with low code coverage have been identified, we could take the help of [~santoshmath] to collect manual test cases covering these packages and go about automating the same. Also, the existing tests are run sequentially and take around 23 minutes to complete on [https://travis-ci.org/apache/fineract.] Along with improving code coverage, we would also have to determine which tests can be run in parallel and enable parallelization to ensure the total time taken is still reasonable. was: While Fineract has integration tests, they currently cover very limited scenarios and code coverage is very low. Enable gradle plugins to report the current code coverage and add new Integration tests to ensure that code coverage, esp in critical packages like loans, savings, and accounting is at-least 50%. Also, the existing tests are run sequentially and take around 23 minutes to complete on [https://travis-ci.org/apache/fineract.] Along with improving code coverage, we would also have to determine which tests can be run in parallel and enable parallelization to ensure the total time taken is still reasonable. > Improve code-coverage to at-least 50% and reduce execution time > --- > > Key: FINERACT-713 > URL: https://issues.apache.org/jira/browse/FINERACT-713 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Vishwas Babu A J >Priority: Major > Labels: gsoc2019 > Original Estimate: 336h > Remaining Estimate: 336h > > While Fineract has integration tests, they currently cover very limited > scenarios and code coverage is very low. > Enable gradle plugins to report the current code coverage and add new > Integration tests to ensure that code coverage, esp in critical packages like > loans, savings, and accounting is at-least 50%. Once the packages with low > code coverage have been identified, we could take the help of [~santoshmath] > to collect manual test cases covering these packages and go about automating > the same. > Also, the existing tests are run sequentially and take around 23 minutes to > complete on [https://travis-ci.org/apache/fineract.] Along with improving > code coverage, we would also have to determine which tests can be run in > parallel and enable parallelization to ensure the total time taken is still > reasonable. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-407) Ability to Re-open closed Accounts (especially Savings and Share Accounts)
[ https://issues.apache.org/jira/browse/FINERACT-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16798419#comment-16798419 ] Vishwas Babu A J commented on FINERACT-407: --- [~edcable] , [~santoshmath] : I have not looked into the dormancy functionality as implemented in Fineract . However , I have read the spec and it isn’t clear if there are accounting entries associated with moving an account to dormancy ( or this is used as just a reporting flag ?). If moving the account to dormancy has accounting entries , then we would have to ask the reporter to use the same instead of closing accounts that are inactive (as long as the funds are moved into a configurable liability account , I am assuming this would meet the needs the reporter is trying to satisfy by closing unused accounts from an accounting perspective ) > Ability to Re-open closed Accounts (especially Savings and Share Accounts) > -- > > Key: FINERACT-407 > URL: https://issues.apache.org/jira/browse/FINERACT-407 > Project: Apache Fineract > Issue Type: Improvement > Components: Savings >Reporter: Ippez Roberts >Assignee: Markus Geiss >Priority: Major > Labels: Fineract-CN, gsoc, p3 > > When a client has not make transactions for many years for example, the MFI > may not know if the client is alive or dead so the MFI can decide to close > this client's Accounts (Savings and Share Accounts). The balances of this > account can be transferred to a GL Account. > Client - GL Transfer: DR Client Accounts and CR. GL Account e.g Share Transfer > After some time, the client surfaces and would like to make transactions on > his accounts. > As a system admin, i should be able to re-open these closed accounts and be > able to transfer the balances from the contra Account back to client's > Savings Account either automatically or manually through batch/journal > Entries where you DR. GL Accounts affected (where the balances are > transferred) and Credit Clients Savings and Share Accounts with the balances > at closure. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINCN-139) Containerization and Deployment of the Apache Fineract CN using Docker.
[ https://issues.apache.org/jira/browse/FINCN-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishwas Babu A J updated FINCN-139: --- Summary: Containerization and Deployment of the Apache Fineract CN using Docker. (was: Containerization and Deployement of the Apache Fineract CN using Docker.) > Containerization and Deployment of the Apache Fineract CN using Docker. > --- > > Key: FINCN-139 > URL: https://issues.apache.org/jira/browse/FINCN-139 > Project: Fineract Cloud Native > Issue Type: Bug > Components: fineract-cn-demo-server >Reporter: Courage Angeh >Priority: Major > Labels: gsoc, gsoc2019 > > * Improve Docker-compose deployment configuration to deploy on a swarm node > * Implement new Fineract service to generate RSA keys and complete the > provisioning process. > * Improve provisioner and migration script to work with both a swarm cluster > and a single machine running multiple compose services > * Build and publish the Fineract images on Docker hub > * Link Docker Hub to Github service repositories via an Automation Server > pipeline > * -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (FINERACT-614) Creation of sub rates
[ https://issues.apache.org/jira/browse/FINERACT-614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable reassigned FINERACT-614: - Assignee: Edward Cable > Creation of sub rates > - > > Key: FINERACT-614 > URL: https://issues.apache.org/jira/browse/FINERACT-614 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Affects Versions: 1.1.0 >Reporter: Angel Cajas >Assignee: Edward Cable >Priority: Minor > Labels: external, p2 > Fix For: 1.4.0 > > > Nominal interest rate for loans can be composed of previously defined > interest rates, When a new loan product or loan account is created you can > choose which rates should apply for the loan. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-689) Able to Create Fixed Deposit/Recurring Deposit product without adding Interest Rate Chart
[ https://issues.apache.org/jira/browse/FINERACT-689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16798029#comment-16798029 ] Santosh Math commented on FINERACT-689: --- [~CJ_Lawrence] , Interest may be anything. The issue here is, adding interest rate chart should be compulsory while creating FD/RD product. > Able to Create Fixed Deposit/Recurring Deposit product without adding > Interest Rate Chart > -- > > Key: FINERACT-689 > URL: https://issues.apache.org/jira/browse/FINERACT-689 > Project: Apache Fineract > Issue Type: Bug > Components: Savings >Affects Versions: 1.2.0 >Reporter: Santosh Math >Priority: Critical > Labels: GSOC, Volunteer, p1 > Fix For: 1.4.0 > > > 1) Go to Admin>Products and select either Fixed Deposit Products or Recurring > Deposit Products and then click on Create Fixed Deposit Product/Recurring > Deposit Product. > 2) Give all mandatory inputs and under 'Interest Rate Chart' provide 'Valid > From Date' and then just submit it without adding interest rate. > > Able to Submit and create FD/RD product without interest rate chart. > Expected: Validation should be thrown 'Interest Rate is not added' , once > submit button is hit. > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
