When testing at scale, it is inevitable that at some point your load test will encounter error states. It may even be a condition itself that is tested. Therefore, it is essential that we have a capability to capture and analyze error information. In this brief article, we will detail how to intercept and log errors in your k6 load tests. Intercepting and Logging Errors Ideally, we would like to save errors to a retrievable logRead More →
Despite our best efforts, we have all been there before. That load test that just concluded generated thousands of errors that it shouldn’t have. It could have been a miscalculation or a shifted decimal place on estimated traffic volumes; or rather it was a configuration setting on the target machines that was overlooked. Regardless, we wish we could have intercepted that test early in its execution, possibly saving valuable time, data charges, and virtual machine costs.Read More →
When running a load test, make sure that your Load Agents are properly sized. We do an automatic “guesstimate” of the number of clients per load agent based on the size of the instance and previous experience. But since every test is different, you need to take a look at the graph at the very bottom of the page to see how the CPU utilization is doing. Here is an example of 25 load agents andRead More →
When writing a Custom test script, you need to add the ability to handle errors. Otherwise, the test script will cause that client to fail. This happens frequently because the request failed by receiving no response or timing out. Once it fails, that user test stops. If you want to continue after an error, you should wrap the goToUrl call in a try/catch. In the catch, add something like: catch (Exception $e) { // Record errorRead More →