Locust.io experiments — running in Kubernetes

Locust supports running load tests on multiple machines. It’s a perfect fit for Kubernetes which makes distributed deployments, container orchestration and scaling easy.
In this installment of my Locust experiments, I’ll prepare Kubernetes (alias…

Locust.io experiments — enriching results

One of the good things about Locust is its event-based nature. This time I’ll try to exploit this to extend the system capabilities with features like custom (non-HTTP) client and results enrichment.

The rationale

Locust.io experiments — running in Docker

Containerizing Locust makes the development of load test easier and — which is more important to me — is a precondition to run Locust on Kubernetes cluster. So, let’s deal with this right at the beginning.

Word of caution

Locust experiments — Feeding the locusts

There are times when you want your Locust scripts to use some specific input data in…

Locust experiments — Locust meets Kafka

This time, let’s teach Locust how to test systems using Apache Kafka.

Locust.io experiments — Emitting results to external DB

Locust.io experiments — extending the UI

Locust provides a small HTTP API and a Web UI to control the execution of the tests and…

Locust Experiments — Docker image updates

Some time ago I did an experiment on dockerizing Locust.

Locust.io experiments — Introduction

Recently we were supposed to conduct a load/stress testing session.

There were already some python scripts in place and the team that produced them suggested using locust.io for this purpose.