You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »


Reference

CPS-1172 - Getting issue details... STATUS


Assumptions

#AssumptionNotes
1


Issues & Decisions

#IssueNotesDecision
1Agree registration performance KPI
  1. Size of request (e.g. 100 cm handles, total size <10Kb)
  2. Concurrent requests for registration (e.g. 4)
  3. Request frequency (e.g. 4 concurrent request each 5 seconds)
  4. Response time of each request (e.g. <4sec)
  5. Single CPS instance
  6. No other workload (module sync 'delayed')
  7. Default resources as defined in our helm charts

2

Agree test environment (talk with Andrew Fenner)

CI Job(s) required?
3Agree technology used to test
  1. Groovy/Spock
  2. CSIT
  3. Python
  4. K6 (not recommended)
  5. Other script using curl?

4Additional requirements to be able to run test

'dummy' DMI PLugin for testing ? (possibly not needed yet for this testcase)




Key Performance Indicators (KPIs)

#

Action

KPINotesDecision
1




Test Environment



Technology Assessments

Here the various technologies will be assessed to determine which can offer the most flexibility, maintainability, and reliability.


Groovy/Spock



CSIT



Python



Curl/Script



Outcomes

#Outcome/ACNotesDone
1

Document proposal on Wiki and share with team and stakeholder



2

Agree with team and stakeholders on options proposed in Spike



References

  • No labels