[jira] [Comment Edited] (FINERACT-1170) Automated Load Testing scenarios & tooling

["James Dailey (Jira)" <ji...@apache.org>]

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

James Dailey edited comment on FINERACT-1170 at 10/21/20, 5:23 PM:
-------------------------------------------------------------------

[~edcable] should definitely weigh in.  In our first generation of Mifos (precursor) we had continuous integration running with a complete data set that could be loaded via a SQL script during build.  That data included PART A and some of PART B below:  

PART A - SETUP 

Import of Clients (Customers) 
Import of all Configs required (GL, Users, Groups, Offices, data scoping, etc) 
Import of Accounts (multiple per client) 
Import of history of Transactions (multiple and dating back several months) 

Then, run: 
 * PART B - CREATE 
Create New Client; 
Create New Product; 
Create New Account (Approve Loan Process); 
Create New Payment Schedule;
Do Disbursement (transaction); 

 * PART C - CREATE ON EXISTING 
Create Transaction on Pre-Existing Client ;
Create Transaction on New Client (repayment);
Advance the date ;
Repeat B & C above ;



PART D - MODIFY 
 * Modify Client Record ;
Modify Client Payments ;
Modify Group Details ;
Modify Product (as allowed by rules) ;



PART E - BATCH JOBS and REPORTS 
Do Batch Jobs
GENERATE Reports 

 
PART F - SCALABILITY & PERFORMANCE TESTING 
 * Multiple Users Signed on 
 * Multiple Accounts being created and modified 
 * Reports running in background 
 * Transactions hitting across 10,000 accounts 
*  Scale resources (processors, memory, I/O) 
 

 


was (Author: jdailey):
[~edcable] should definitely weigh in.  In our first generation of Mifos (precursor) we had continuous integration running with a complete data set that could be loaded via a SQL script during build.  That data included: 

PART A - SETUP 

Import of Clients (Customers) 
Import of all Configs required (GL, Users, Groups, Offices, data scoping, etc) 
Import of Accounts (multiple per client) 
Import of history of Transactions (multiple and dating back several months) 

Then, run: 
 * PART B - CREATE 
Create New Client; 
Create New Product; 
Create New Account (Approve Loan Process); 
Create New Payment Schedule;
Do Disbursement (transaction); 

 * PART C - CREATE ON EXISTING 
Create Transaction on Pre-Existing Client ;
Create Transaction on New Client (repayment);
Advance the date ;
Repeat B & C above ;



PART D - MODIFY 
 * Modify Client Record ;
Modify Client Payments ;
Modify Group Details ;
Modify Product (as allowed by rules) ;



PART E - BATCH JOBS and REPORTS 
Do Batch Jobs
GENERATE Reports 

 
PART F - SCALABILITY & PERFORMANCE TESTING 
 * Multiple Users Signed on 
 * Multiple Accounts being created and modified 
 * Reports running in background 
 * Transactions hitting across 10,000 accounts 
*  Scale resources (processors, memory, I/O) 
 

 

> Automated Load Testing scenarios & tooling
> ------------------------------------------
>
>                 Key: FINERACT-1170
>                 URL: https://issues.apache.org/jira/browse/FINERACT-1170
>             Project: Apache Fineract
>          Issue Type: New Feature
>            Reporter: Michael Vorburger
>            Priority: Critical
>              Labels: scalability
>
> During [ApacheCon @Home Sep 29 - Oct 1, 2020|https://apachecon.com/acah2020/index.html], in a number of [sessions on the Fineract track|https://apachecon.com/acah2020/tracks/fineract.html], including:
>  * the BOFs,
>  * the "[To Infinity and Beyond: Scaling Fineract for the Enterprise|https://docs.google.com/document/d/18pdICOm8jEZN5VI7MuHJK_jLO2UCu_NJMYivm0QAQOo/edit]" panel
>  * the "[Running Fineract.dev|https://docs.google.com/presentation/d/1-VP4bNkc5kZ3B0yme_vYLiY1qpswnfz8ainnX5fp3l8/]" presentation
> We have spoken about Fineract scalability ideas, and possible next steps.
> We have identified that what we require most as a community to progress on Fineract scalability (see [our JIRA issues with 'scalability' label|https://issues.apache.org/jira/issues/?jql=labels%20%3D%20scalability%20and%20project%20%3D%22Apache%20Fineract%22%20]) is a Automated Load Testing scenarios & tooling.
> Tools suitable to build this include [JMeter|https://jmeter.apache.org], [Gatling.io|https://gatling.io], perhaps even simply [Postman|https://www.postman.com/] with [Newman|https://github.com/postmanlabs/newman].
> We would, ideally, like for this to eventually run in our CI.
> FYI [~avikg] ([~avikganguly]? [~avikganguly010]?), [~vromero] ([~Fintecheando]?), [~aleks], [~edcable], [~jdailey] ([~jamespdailey]), Istvan not on JIRA?



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