[jira] [Updated] (FINERACT-1170) Automated Load Testing scenarios & tooling
[ https://issues.apache.org/jira/browse/FINERACT-1170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Vorburger updated FINERACT-1170: Priority: Critical (was: Blocker) > 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)
[jira] [Updated] (FINERACT-1170) Automated Load Testing scenarios & tooling
[ https://issues.apache.org/jira/browse/FINERACT-1170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Vorburger updated FINERACT-1170: Priority: Blocker (was: Major) > 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: Blocker > 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)
[jira] [Updated] (FINERACT-1170) Automated Load Testing scenarios & tooling
[ https://issues.apache.org/jira/browse/FINERACT-1170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Vorburger updated FINERACT-1170: Labels: scalability (was: ) > 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: Major > 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)
