With loadforge-cli, your Locust scripts and test configs can live in Git, and your automations (syncing tests, starting runs, waiting for results) live in GitHub Actions. It’s the fastest way to make load testing part of your development workflow.
Writing the same Python helpers across multiple Locust tests is brittle and slow. The Library lets you create shared Python modules—small, reusable functions you can import across all your tests—to keep your performance suite DRY and consistent.
TLDR: New updates include a tagging system for tests, a field for run owners, a description field for notes, and an automated testing option with pre-made scripts for easier test management and creation.
•1 min read
We've got a heap of new updates for you, focused on multi-user organizations and easier test creation.
Tag System
We have added a tagging system for Tests, allowing you to attach any number of tags to your load tests. You can then filter on them, both on the test management page and the run results page.
Run Owner
We've added a user field to runs, so you can see who started a run on the Run list.
Descriptions
You can keep arbitrary notes and descriptions on any Web Test in the new Description field.
Automated Tests
You can now choose between the normal advanced editor, and the automated test system. A simplified version of tests that provides several pre-made test scripts to test basic functionality on a variety of apps.