The purpose of this project is to gather a curated set of plugins/extensions for Locust.

Locust itself is a "bare bones" load generation tool (compared to for example JMeter or Gatling) and it is left to the user to build even basic functionality (like reading test data from a database, using non-HTTP protocols, etc). This keeps Locust lean and mean, but forcing everyone to reinvent the wheel is not good either.

So I decided to publish my own plugins and hope that others (maybe you?) will contribute their solutions to common Locust use cases.

Having this separate from "Locust core" allows the plugins to evolve faster (at the expense of being less mature), and avoids bloating Locust with functionality you might not be interested in.

pip install locust-plugins

Most settings are configured from code, but some are exposed as command line arguments. You can list them by using Locust's regular --help argument:

locust --help

• Listen to events and log things
  • Timescale: Log and graph results using TimescaleDB and Grafana dashboards (readme, source)
  • Jmeter: Writes a jmeter-like output file (example, source)
  • ApplicationInsights: Writes the test logs to Azure Application Insights (example, source)
  • RescheduleTaskOnFail / ExitOnFail / StopUserOnFail: Perform actions when a request fails (source)

• New protocols (source)
  • Playwright (example)
  • WebSockets/SocketIO (example)
  • Selenium/Webdriver (example)
  • HTTP users that load html page resources (example)
  • Kafka (example)
  • MqttUser (example)
  • RestUser has been removed, as it is now part of locust core!

• Provide ways to get test data into your tests
  • CSV (example, source)
  • MongoDB (example, source)

• Custom wait time functions (example, source)

• Support for distributing test data from master to workers while maintaining test data order (example, source)

• Support for logging transactions (aggregating multiple requests or other actions) (example, source)

• Allows users to occupy more ports when running tests, useful for dealing with strange behaviour from load balancers in low user count high throughput scenarios. scenarios. (example, source)

• Additional locust command line options provided (examples, source)
  • Iteration limit (-i), stops Locust after a certain number of task iterations
  • Checks (--check-rps, --check-fail-ratio, --check-avg-response-time), gives an error return code if certain conditions are not met
  • Dashboards (--timescale, --grafana-url, --pghost, ...)

Have a look at the example locustfiles to learn how to use the plugins.

These plugins work well together with locust-swarm

Contributions are very welcome! 😁

For guidelines, see CONTRIBUTING.md

Copyright 2019 AB SvenskaSpel

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

https://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.