Reference
- CPS-1172Getting issue details... STATUS
Assumptions
# | Assumption | Notes |
---|---|---|
1 |
Issues & Decisions
# | Issue | Notes | Decision |
---|---|---|---|
1 | Agree registration performance KPI |
| |
2 | Agree test environment (talk with Andrew Fenner) | CI Job(s) required? | |
3 | Agree technology used to test |
| |
4 | Additional requirements to be able to run test | 'dummy' DMI PLugin for testing ? (possibly not needed yet for this testcase) |
Key Performance Indicators (KPIs)
Contact Toine Siebelink, Tony Finnerty, & kieran mccarthy
# | Action | KPI | Notes | Decision |
---|---|---|---|---|
1 |
Test Environment
TBD
Contact Andrew Fenner
Technology Assessments
Here the various technologies will be assessed to determine which can offer the most flexibility, maintainability, and reliability.
Groovy/Spock
There is an existing Groovy/Spock performance test located in org.onap.cps.ri.performance.CpsToDataNodePerfSpec that could be used as the basis for this...
- CPS-1351Getting issue details... STATUS
# | Pros | Cons | Notes |
---|---|---|---|
1 |
|
|
|
CSIT
# | Pros | Cons | Notes |
---|---|---|---|
1 |
|
|
Python
# | Pros | Cons | Notes |
---|---|---|---|
1 |
|
Curl/Script
# | Pros | Cons | Notes |
---|---|---|---|
1 |
K6
# | Pros | Cons | Notes |
---|---|---|---|
1 |
Outcomes
# | Outcome/AC | Notes | Done |
---|---|---|---|
1 | Document proposal on Wiki and share with team and stakeholder | ||
2 | Agree with team and stakeholders on options proposed in Spike |
2 Comments
Gergely Molnar
I would suggest to consider JMeter, which is easily configurable in terms of request size, thread count, loop count and the response times and other metrics can be evaluated easily.
As a modern alternative, k6 could also be considered.
Joseph Keenan
Thank you Gergely, K6 will be considered for this spike.