In this tutorial, we will look into how to integrate performance testing with k6 into your Jenkins Pipeline setup. By integrating performance tests into your CI pipelines, you can catch performance issues earlier and ship more stable and performant applications to production.
Before the release of k6 v0.27, there was insufficient support for generating constant request rates. Therefore, we introduced a JavaScript workaround by calculating the time it takes for requests to exhaust each iteration of the script. This v0.27 release includes a new execution engine and lots of new executors that cater to your specific needs. It also includes the new scenarios API with lots of different options to configure and model the load on the system under test.
k6 v0.27.0 is finally out! It has been over a year since the k6 team started working on this release, which includes a multitude of new features, improvements, bugfixes and beyond. This release was an effort to redefine performance and load-testing in k6, by introducing a new execution engine and lots of new executors on top, along with the most requested feature, scenarios. It also includes many UX improvements and bugfixes.
As outlined in our rebranding announcement post from Feb 24th, today we're disabling access to v4 projects in the LoadImpact web app at app.loadimpact.com (v3 projects will continue to be available until Dec 31st, 2020). All v4 projects, tests, and test results will henceforth only be accessible from app.k6.io. The same login credentials are valid across the two web apps. Rest assured, no data is going away, it's technically an older of two frontends being sunsetted.
If you want to jump straight to installing the marketplace extension, you can find it here. Performance issues can quickly turn expensive. Reasons can vary from unexpected traffic surges, pieces of non-performant code acting as bottlenecks, or misconfigured network components. Integrating load- and performance testing into your CI pipeline will allow you to know about performance degradations early, in most cases, even before it has any impact on your users in the production environment.
This article demonstrates how to Load Test an application deployed in a Kubernetes cluster, verify that the autoscaling is working, and identify potential performance bottlenecks. When you deploy an application to production on Kubernetes, you'll need to monitor traffic and scale up the application to meet heavy workloads during various times of the day. You'll also need to scale down your application to avoid incurring unnecessary costs.
In this article, I'll explain how to use a Postman collection I have created to load test our instance of our test API. The process is pretty straightforward, as is shown below. You need to feed your exported Postman collection to our postman-to-k6 converter, and use the generated k6 script to load test your own API.
At the end of 2018, Microsoft stated that Visual Studio 2019 is the last version with load testing features. A few months later they formally announced that Azure load testing is closing down on March 31st, 2020. This announcement came as a bomb to the community. But for those who follow this market, the news was not a complete surprise.
In this tutorial, we will look into how to integrate performance testing with k6 in your TeamCity build setup. k6 is a free and open-source performance testing tool for testing the performance of APIs, microservices and websites. TeamCity is a continuous integration and delivery server built by JetBrains.
Throughout the years, there has been many attempts to devise a universal format for defining Web API specifications. The objective was (and still is) to help stakeholders of the system to work with those APIs, without having access to the source code. Each new "universal" format came with the promise of being ubiquitous and all-encompassing, but eventually faded away due to various reasons, like OData and WSDL.
