Whats Carrier io Continuous Test Automation Framework Opensource software httpsgithubcomcarrieriocarrierio Containerbased solution that makes integration with CICD pipeline conceptually simple ID: 1041773
Download Presentation The PPT/PDF document "FOLIO – Carrier- io Integration" is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
1. FOLIO – Carrier-io Integration
2. What’s Carrier-io?Continuous Test Automation FrameworkOpen-source software https://github.com/carrier-io/carrier-ioContainer-based solution that makes integration with CI/CD pipeline conceptually simpleA suite of tools that profile, collect metrics, and visualize performance testing resultsLoad Generator: JMeter, PerfMeterProfiler: Uber JVM ProfilerStorage: Influx DatabaseMetrics collector: TelegrafVisualizing Tool: GrafanaData collect:High API-level response times and throughputKey system metrics on container level, such as CPU and memory utilization, disk and network data transfersJava methods execution times
3. Why Carrier-io?Integrates with the CI/CD pipeline to give quick feedback on performance, comparative analysis between test runs, quick analysis of performance bottlenecks.How?Modifying the modules’ docker-entrypoint.sh to download the profiler, configure Influx database endpointAdding a few Jenkins stages to the CI/CD pipeline One Jenkins stage launches a spot instance that has JMeter and load generator installed to run the test. Second Jenkins stage tears down the spot instance when the test run is over. The last Jenkins stage sends results to email or Slack.
4. Test Modelling
5. TestsEnvironment:DB: db.r5.xlargeEC2 instances: m5.large (x3)Modules are distributed over the 3 EC2 instances by ECS algorithmQ3.2 FOLIO release, using 287K inventory records dataset.Variations of Capacity Test simulating Checkout and Check-in workflows1 virtual user is added every 30 seconds for the duration of 30 minutesInflection point at 40 users40 TPSPotential smoking gun with OKAPI. The OKAPI’s container CPU utilization is at 90% starting with 10 vUsersorg.folio.okapi.util.LockedStringMap.getString()Repeated with only Checkout, Check-in, and GetItems tests, seeing same results
6. Results
7.