stress-test-locust

KO | EN

gitlite — search

#javascript #python #hacktoberfest #react #ai #golang #deep-learning #macos #windows #awesome #cli #kubernetes #ios #mcp

stress-test-locust

(★ 50)

Template for stress testing with Python, Locust & Docker

stress-test-locust Latest Version Download

Download Latest Version (.zip)

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# Stress testing with Locust

</div>

## Description

[Locust] is a distributed and scalable open-source library that helps you write effective
load tests in pure Python. This repository demonstrates a modular architecture that can work
as a template for quickly building a scalable stress testing pipeline with Locust.

## Locust terminology

If you're unfamiliar with the terminologies and the general workflow of stress testing with
Locust, then I recommend going through the official [documentation] first. With that out of
the way, let's rehash a few terminologies that come up in this context quite often:

**Task:** In Locust, a [Task] is the smallest unit of a test suite. Usually, it means, any
function or method that is decorated with the `@task` decorator.

**TaskSet:** A [TaskSet] is a class that establishes a contextual boundary between different
groups of Tasks. You can essentially group multiple similar Tasks inside a TaskSet. Then you
use the TaskSets from your User class.

**User:** In Locust, a [User] is a class that executes the tests either directly calling the
Task methods or using TaskSets.

**_In more complex cases, the tests can further be organized by arranging them in multiple
test modules. This template groups the Tasks using TaskSets and places multiple TaskSets in
separate test modules to achieve better modularity._**

## Target API

Here, we're using [Rapid API]'s currency exchange [API] to showcase the load testing
procedure. The API converts one currency to another using the current exchange rate.

### API anatomy

It takes three parameters in its query string:

```txt
1. q    : str - quantity
2. from : str - currency to convert from
3. to   : str - currency to convert to
```

And returns the converted value.

### Access the API

Sign up for a Rapid API [account] and get your token. You can access the API via cURL like
(You need to provide your API token in the header):

```sh
curl --request GET \
     --url 'https://currency-exchange.p.rapidapi.com/exchange?q=1.0&from=USD&to=BDT' \
     --header 'x-rapidapi-host: currency-exchange.p.rapidapi.com' \
     --header 'x-rapidapi-key: your-api-token'
```

The response will look like this:

```txt
84.91925⏎
```

Or, you might want to access it via Python. You can do so using the [HTTPx] library like
this:

```python
import httpx

url = "https://currency-exchange.p.rapidapi.com/exchange"

querystring = {"q": "1.0", "from": "USD", "to": "BDT"}

headers = {
    "x-rapidapi-host": "currency-exchange.p.rapidapi.com",
    "x-rapidapi-key": "your-api-token",
}

with httpx.Client(http2=True) as client:
    response = client.get(url, headers=headers, params=querystring)

print(response.text)
```

## Stress testing pipeline

Below, you can see the core architecture of the load testing pipeline. For brevity's sake,
files regarding containerization, deployment, and dependency management have been omitted.

```txt
src/
├── locustfiles         # Directory where the load test modules live
│   ├── __init__.py
│   ├── bdt_convert.py  # Load test module 1
│   └── rs_convert.py   # Load test module 2
├── __init__.py
├── auth.py             # Auth, login, logout, etc
├── locust.conf         # Locust configurations
├── locustfile.py       # Locust entrypoint
└── settings.py         # Read the environment variables here
```

The test suite has three primary components: `setup.py`, `locustfiles`, and the
`locust.conf` file.

### [setup.py](src/setup.py)

The common elements required for testing, like `auth`, `login`, and `logout` functions
reside in the `setup.py` file.

### [locustfiles](src/locustfiles/)

The load test modules reside in the **`locustfiles`** directory. Test modules import and use
the functions in the `setup.py` file before executing each test.

In the `locustfiles` folder, currently, there are only two load test modules—
`bdt_convert.py` and `rs_convert.py`. You can name your test modules whatever you want as
long as the load testing classes and functions reside here.

-   [bdt_convert.py](src/locustfiles/bdt_convert.py): This module houses a single TaskSet
    named `BDTConvert` that has two Tasks—`usd_to_bdt` and `bdt_to_usd`. The first Task
    tests the exchange API when the request query asks for USD to BDT currency conversion
    and the second Task tests the API while requesting BDT to USD conversion.

-   [rs_convert.py](src/locustfiles/rs_convert.py): The second test module does the same
    things as the first one; only it tests the APIs while the request query asks for USD to
    RS conversion and vice versa.

The reason that there are two similar test modules is just to demonstrate how you
        can organize your Tasks, TaskSets, and test modules.

-   [locustfile.py](src/locustfile.py): This file works as the entrypoint of the workflow.
    It imports the TaskSets from the `bdt_convert` and `usd_convert` modules and creates a
    [HttpUser] that will execute the tasks.

### [locust.conf](src/locust.conf)

The **`locust.conf`** file defines the configurations like _hostname_, _number_ of
_workers_, _number of simulated users_, _spawn rate_, etc.

## Run the stress tests locally

-   Make sure you have the latest version of [docker] and docker-compose installed on your
    machine.

-   Clone this repository and go to the root directory.

-   Place your rapidAPI token in the `.env` file.

-   Run:

```sh
    docker compose up -d
    ```

This will spin up a master container and a single worker container that will do the
    testing. If you want to deploy more workers to do the load testing then run:

```sh
    docker compose up -d --scale worker 2
    ```

-   To access the Locust GUI, go to [http://localhost:8089/] on your browser. You'll be
    greeted by a screen like below. You should see that the fields of the form are already
    filled in since Locust pulls the values from the `locust.conf` file:

![locust-signin]

-   Once you've pressed the _start swarming_ button, you'll be taken to the following page:

![locust-dashboard]

-   You can start, stop, and control your tests from there.

## Disclaimer

This dockerized application is production-ready. However, you shouldn't expose your
environment file (.env) in production. Here, it was done only for demonstration purposes.

[locust]: https://locust.io/
[documentation]: https://docs.locust.io/en/stable/
[task]: https://docs.locust.io/en/stable/writing-a-locustfile.html#tasks
[taskset]: https://docs.locust.io/en/stable/writing-a-locustfile.html#tasksets
[user]: https://docs.locust.io/en/stable/writing-a-locustfile.html#user-class
[rapid api]: https://rapidapi.com/
[api]: https://rapidapi.com/fyhao/api/currency-exchange
[account]: https://rapidapi.com/signup
[httpx]: https://github.com/encode/httpx
[httpuser]: https://docs.locust.io/en/stable/writing-a-locustfile.html#making-http-requests
[docker]: https://www.docker.com/
[http://localhost:8089/]: http://localhost:8089/
[locust-signin]:
    https://user-images.githubusercontent.com/30027932/92285103-51988580-ef25-11ea-9155-c9d3f5dcaf42.png
[locust-dashboard]:
    https://user-images.githubusercontent.com/30027932/92285284-b94ed080-ef25-11ea-9f91-3f972fd844f1.png

stress-test-locust

stress-test-locust Latest Version Download

Today's picks

Was this content helpful?

Recent Feedback

stress-test-locust

stress-test-locust Latest Version Download

Today's picks

Was this content helpful?

Recent Feedback

Download README