Hi there, Here at k6, we’re constantly shipping new features to help our users get the most out of k6. In case you missed it, here’s a roundup of all the k6 and k6 Cloud news, updates, and improvements you should know about.

With version 0.41, k6 has changed how it handles, stores, and aggregates the data it collects in the context of a load test. Most users probably won't notice any immediate difference. Yet, we expect these changes will empower us to make k6 more performant and easier to integrate into the larger observability ecosystem.

This tutorial will demonstrate Keptn, a CNCF Incubator Project’s integration with k6. Keptn is a cloud-native application delivery and operations platform. We will use the Job Executor Service to execute k6 performance testing in a Keptn project. We'll start with running a k6 script and how the logs look. And then we'll modify the k6 script to see the behavior when it fails.

At ObservabilityCON, we announced our first step towards launching a native integration between Grafana k6 load testing and Grafana Tempo tracing (k6 x Tempo) in Grafana Cloud. We created k6 x Tempo to help dev, testing, and operation teams analyze their performance test results more effectively and proactively improve the reliability of their business-critical applications.

The growth of a code base is unpredictable. To account for this uncertainty, we call on everything we've learnt in the last x years about how to scale an application effectively: adopting naming conventions, creating file and folder structures, using the latest patterns, and producing sensible abstractions. These actions add up over time. Eventually, you'll mentally high-five your past self for having taken the time to do them ✋.