We have already wrote previously about how you can automate your testing routines without using the graphical interface but by using Loadero API instead. In this blog post we will show how you can integrate performance and load tests into your CI/CD workflows with the help of Github Actions. Github Actions allow you to automate and execute your development workflows directly from your repository which makes the integration very simple.

Recently, k6 started supporting k6 extensions to extend k6 capabilities for other cases required by the community. The community has already built plenty of extensions. k6 extensions are written in Go, and many of them are reusing existing Go libraries. This makes k6 to be a versatile tool to test different protocols and adapt to multiple cases. This post is the third part of my series of articles testing various systems using k6: Let's look in this post how we test the popular Kafka project.

The summer break is over, we start to creep towards autumn, and we at k6 haven't been resting on our laurels. What happened since the k6 v0.33.0 release? So glad you asked! The below. And then some!

You can find a collection of k6 scripts and build specification for CodeBuild in this tutorial here.

In this tutorial, we will look into how to integrate performance testing in your development process with Google Cloud Build and k6. k6 is an open-source load testing tool for testing the performance of APIs, microservices, and websites. Developers use k6 to test a system's performance under a particular load to catch performance regressions or errors.

August was a month with multiple vacations in our team, but it didn’t make our work lag. Some important changes were made last month and we are glad to announce how we improved our tool recently and what you can do to make your Loadeo tests even better, more relevant and insightful.