A k6 load test can generate a ton of data. Without a way to organize the data, you'll struggle to analyze test results. Fortunately, there are many ways to turn results into data-rich visualizations.

Screen sharing is not just common nowadays, it is present in many different apps we use. Webinar applications allow presenters to share their screen with the audience, video calling and conferencing apps allow sharing your screen to show other attendees the information you need to share, e-learning is a lot more effective when teachers can see what’s happening with their student’s screen, the list goes on and on.

Software development is entirely different today than it was a few years ago. Back then, we usually had a big monolith running on our own hardware. We mainly did performance tests to see if the hardware resources were sufficient to handle the load. Today, we develop software in a distributed environment with multiple services which may even run on different cloud platforms. With performance testing, we try to identify performance and resilience issues in these kinds of environments.

During crucial performance testing session we need to monitor and measure various parameters/metrics to be able to analyze and understand why the application behaves in a certain way under a specific load. Below ones are the most used metrics collected during performance testing sessions.

Software developers try to implement applications that not only is responsive and fast with a very small number of users but also with multiple users using the application. To be able to measure this we need to rely on different types of performance testing. Performance testing should be an integral part of the agile release manifesto.

With over a billion more mobile devices projected to become connected over the next year, it’s never been more important to ensure SLA performance and functional reliability for business-critical APIs. While QA, development, and SRE teams have traditionally relied on API load testing and uptime or ping monitors to mitigate performance risk, too many companies have felt the pain of APIs, mobile apps and web platforms failing under stress or unexpected traffic patterns.

You can find a collection of k6 scripts and GitHub workflows referenced in this tutorial here. In this tutorial, we will look into how to integrate performance testing in your development process with GitHub Actions and k6. For a video tutorial 🎥 , check out the following tutorial on YouTube. k6 is an open-source load testing tool for testing the performance of APIs, microservices, and websites.

Just because your app or site works great in the lab doesn’t mean it will perform that way for end-users. Performance testing is essential to understanding how your website or application will behave in the real world. While error testing is about finding bugs in your software, performance testing is about ensuring your code works as intended and delivers the results you expect when a very high number of end-users are attempting to access your service at the same time.

Last month of winter is over and the spirit of spring is already in the air. We did a lot of work to improve Loadero last month, but the last week of February was filled with shocking events for us, as it was for the whole world. We support the people of Ukraine suffering from what happens in their country right now and every day we hope that it ends soon. There is nothing more important than peace, and we hope it will be restored soon.

At k6 we regularly get a request to support another programming language in addition to JavaScript. Go developers would like to write test scripts in Go, Java developers migrating from jMeter would like to write tests in Java. We have evaluated these requests and discussed in detail internally if this is a good direction for the k6 tool. Ultimately we have decided against supporting more programming languages for scripting. Below is our reasoning for this decision.