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.
Testing, by its nature, isn’t the real world. Still, you can make your load tests more realistic. Besides following our general advice about better load tests - like using the LoadImpact plugin for Google Chrome to record user scripts that emulate frequently-used features - we’d like to suggest another tips that might make your tests even better.
When we talk about load testing, it’s easy to focus on consumer e-commerce. It’s convenient for examples, and we can all think of straightforward ways load testing might benefit during peak seasons like Black Friday. But you, as a developer, are doing yourself and your company a disservice if you’re focusing entirely on your consumer customer experience. Don’t overlook your B2B (business-to-business) performance as well.
With the new k6 HAR converter, it is dead simple to use a browser to record a user session and then let k6 replay it in a load test. This article describes the HAR converter feature and how you can use it.
A Practical Guide to Testing in DevOps offers direction and advice to anyone involved in testing in a DevOps environment.
No matter how experienced you are, it’s easy to get terms mixed, confused, and misunderstood. To help, we’ve prepared this brief primer on performance testing vs stress testing to define these common terms (and a few others). You may still hear some of these terms used interchangeably, but at least now you have ammunition to correct others when you’re feeling pedantic. <grin> Let’s start with load testing.
We recently talked about the “new” shift left testing trend. The concept is important, for sure, especially in a larger, less nimble development organization. But all testing, we believe, should be developer-first.
Check out this video recording, where we cover the basics of load testing and how to build an automation pipeline using Jenkins executing tests on LoadImpact.com. In the end we'll take a peak view on our next major platform upgrade, built on top of our open source load testing tool - k6
The phrase “shift left” testing has gained some recent traction. But what does “shift left” mean for you? In short, it means what you already know: the earlier you test, the better, and you should test consistently and continuously.