This article is the fourth part of a series of tutorials dedicated to Gatling Load Testing. Kraken is used to ease the debugging of Gatling simulations and to speed up the process of load testing a fake e-commerce website: PetStore. We will focuse on POST requests and script modularization: In the previous blog post we created a realistic Virtual User that browses the store without buying anything.
This third version of Kraken represents one more step towards a load testing solution suitable to teams and enterprises. Kraken can already be installed on your own Kubernetes cluster thanks to Helm charts: You own all data and can handle the security inhouse. But until now it was lacking users management, making it cumbersome to use it for a team of performance testers. This point is now addressed in the version 3.0 thanks to Keycloak.
OctoPerf’s report engine provides many graphs to sort and presents test metrics in a comprehensive way. We’ve tried to improve it over the years so that you can access critical information very quickly. But requirements vary from one project to the other. In this post we will look at how you can configure the report to show you preferred metrics, and also all the shortcuts you can take to achieve this goal.
Here we are for yet another new release of OctoPerf. We’ve actually released two minor versions since the last update post, but this time we will also release a long awaited feature, Microsoft Azure on demand load generators!
