Most companies have moved or are in the process of moving at least part of their infrastructure to the cloud. This movement to the cloud has made it commonplace for things like continuous integration, automation, containerization, and continuous testing among other things. From working with customers on test automation and continuous testing, we have found one myth that we wanted to educate others on.
MYTH: Load testing isn’t necessary when moving to k8s because they’re going to automatically scale for you.
MYTH BUSTER: Although moving to a Kubernetes clustered environment will automatically scale for you, there is still configuration and maintenance you need to do in order to setup your cluster to scale appropriately and should be load tested.
In this case study, you will see how a Testery customer busted the above myth with load testing. In this case study you will learn:
- Load tests exposed performance degradation due to issues with the setup of their Kubernetes clustered environment, inefficiencies in the code and a few bugs
- How they more than doubled their load capacity (with the ability to easily scale further if needed) and reduce some page load times by more than 75%
- How they worked with us to get an automated testing framework in place, and add smoke tests increasing code coverage
- Re-using smoke tests in load testing reduces level of effort, time and cost to put load tests into place