✳flâneur — a map of the web's best reading

Your first test — Locust 2.31.6 documentation

docs.locust.io · 584 words · saved by 1 readers

A Locust test is essentially just a Python program making requests to the system you want to test. This makes it very flexible and particularly good at implementing complex user flows. But it can do simple tests as well, so let’s start with that: This user will make an HTTP request to /hello, then to /world, and then repeat. For a full explanation and a more realistic example see Writing a locustfile. Change /hello and /world to some actual paths on the website/service you want to test, put the code in a file named locustfile.py in your current directory and then run locust: Open http://localhost:8089 The following screenshots show what it might look like when running this test using 50 concurrent users, with a ramp up rate of 1 user/s Note Interpreting performance test results is quite complex (and mostly out of scope for this manual), but if your graphs start looking like this, the target service/system cannot handle the load and you have found a bottleneck. When we get to around 20

Your first test - Locust 2.46.2.dev0 documentation Your first test Your first test  A Locust test is essentially just a Python program making requests to the system you want to test. This makes it very flexible and particularly good at implementing complex user flows. But it can do simple tests as well, so let’s start with that: from locust import HttpUser , task class HelloWorldUser ( HttpUser ): @task def hello_world ( self ): self . client . get ( "/hello" ) self . client . get ( "/world" ) This user will make an HTTP request to /hello , then to /world , and then repeat. For a full explana

Explore this link on the map →

related reading