Update locust get started blog for current version - #175
Merged
Merged
Conversation
phil-davis
reviewed
Aug 12, 2026
phil-davis
previously approved these changes
Aug 12, 2026
There was a problem hiding this comment.
Pull request overview
Updates the “Locust - 01 - Get Started” blog post so newcomers can follow along using the current Locust package name, API surface, and updated web UI.
Changes:
- Updates installation instructions from
locustiotolocust. - Refreshes the sample
locustfile.pyto useHttpUser/tasks(newer Locust API style). - Updates UI walkthrough text and screenshot to match the current “Start new load test” screen.
Suppressed comments (3)
src/assets/Locust/locust-01.md:62
- Minor grammar: start the sentence after the colon with a capital letter for consistency with the other bullets.
- **Ramp up (users started/second)**: the rate at which Locust starts new users.
src/assets/Locust/locust-01.md:69
- Typo: "ram up" should be "ramp up".
Choose e.g., 20 users to simulate, 2 users/s for ram up and 2m for run time. Then start the load test.
src/assets/Locust/locust-01.md:71
- Grammar: "Logs" should be singular ("tab"), and the verb should agree ("tab shows").
On the main screen, you will now see some statistics about the number of requests, and how long they took. On the "Charts" tab, you will find the same data over time in a nice graph. "Failures" and "Exceptions" should be empty, because all the requests should have succeeded. The "Current Ratio" tab shows the current distribution of requests across tasks. Under "Download Data", you get the data as nice CSV files while the "Logs" tabs shows Locust's runtime logs.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
individual-it
approved these changes
Aug 12, 2026
phil-davis
approved these changes
Aug 12, 2026
fix typo address review Signed-off-by: Salipa-Gurung <salipagurung@gmail.com>
Salipa-Gurung
force-pushed
the
update-locust-blog
branch
from
August 12, 2026 13:17
0874115 to
eb70784
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation And Context
Key Message
Update the first Locust blog in the series to work with the current Locust version and UI.
Target Audience
Developers and testers who are new to performance testing with Locust.
Current Status
Declaration Of Sources
(e.g. images, illustrations, quotations from other blogs and publications, etc.)