Load testing is a leading indicator. In business and economics, a leading indicator is something that suggests a greater change is about to come. We can apply that concept, too, to load testing: load testing’s a leading indicator of greater issues in your app or site.
Ever since the first early beta release, some 10 months ago, the team has worked hard to iron out bugs and scale the streaming and analysis of k6 results data, and now we’re here! 🎉
Many people have started using k6 to test their web services and APIs, but not all are aware of the different results output options offered by k6. This article shows how simple it is to use Grafana to visualise your k6 test results.
Congratulations: you’ve run a few LoadImpact load tests and you’re anxiously poring over the results. You’ve probably already gained a few insights about what you might improve. You’ve seen some areas you want to explore further. And you’ve found some mysterious status codes in the URLs tab on the test results page.
Join our webinar where we'll describe the difference between Load Impact Insights, our new analysis solution, versus the way results are handled in the current load testing platform. We will continue to reveal features that will be part of our next major platform upgrade, built on top of our open source load testing tool - k6
When you look at results, you will first want to start with the main graph, you can derive a lot of information from it! By default, we will plot two metrics - Virtual Users (VUs) and Virtual User Load Time. By definition VU Load Time is a measure of how long it takes a virtual user to make all the HTTP requests during an iteration of the user scenario they are assigned to. If you are running a simple URL test, you’ll probably get results in milliseconds. If you recorded a long journey with our chrome extension, you may be looking at minutes.
We’ve come across more and more engineers who utilize dynamic URLs throughout their websites and applications over the last year.