This release contains the work of over 10 contributors split over more than 100 commits. v0.29.0 contains a whole bunch of new, exciting features. We hope that you'll enjoy it as much as we do! Read the full release notes here.

I used the K6 load testing framework to benchmark the Compute Engine f1-micro and Caddy web server hosting this site. With CloudFlare caching turned off, the server was able to serve an onslaught 800 virtual users continuously reloading the page (while maintaining a median request duration of <400ms), but started dropping requests when increasing the load further. This is fine.

In this tutorial, we will look into how to integrate performance testing with k6 into your GitLab setup. By integrating performance tests into your CI pipelines, you can catch performance issues earlier and ship more stable and performant applications to production.

In this tutorial, we will look into how to integrate k6 tests into CircleCI. By integrating performance tests into your CI pipelines, you can catch performance issues earlier and ship more stable and performant applications to production.

The outline of this article is as follows: Most systems are designed to treat users differently based on their identity. Therefore, users are authenticated via various mechanisms and it's often equally important to test the performance of anonymous and authenticated endpoints. One of the most widespread authentication standards used by today's applications is OAuth. In OAuth, we use a trusted third party to verify the identity of the user.

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.