The cloud version is just for demo purposes. It is recommended that you download and install TeamCity for your OS. The Continuous Integration tool we are going to use in this tutorial is TeamCity. The content of a response must be correct more than 95% of the time.Ĭheck out the Thresholds documentation for extended information about the API and its usage.
The 95th percentile response time must be below 400 ms. The 99th percentile response time must be below 700 ms. Thresholds is a powerful feature providing a flexible API to define various types of Pass/Fail criteria in the same test run. By design, this is a very simple script for illustrative purposes. The following test will run 50 Virtual Users continuously for a period of one minute, each VU execution generates one request and sleep for a period of 3 seconds. Next clone the repo to your local hard drive in order to start writing tests. Let's start by creating a new repo using your favorite remote repository platform. Your tests should be focused on endpoints and architecture that are important to your business. To start, we will create a simple k6 test for our demo API. This is necessary for TeamCity server to run k6 commands during the build step. In order to follow along, you'll need to install k6 CLI locally on your host machine. TeamCity is a continuous integration and delivery server built by JetBrains. K6 OSS is an open-source load testing tool for testing the performance of APIs, microservices and websites. In this tutorial, we will look into how to integrate performance testing with k6 in your TeamCity build setup. Integrating performance tests into your CI pipelines helps catch performance issues earlier and shipping more stable and performant applications to production.
Different implementation paths, and when to use each. How to detect performance issues earlier. How to integrate load testing with k6 into TeamCity.
0 kommentar(er)
