支持通过配置文件运行realbrowserlocusts压测的Locust版本查询及realbrowserlocusts升级计划咨询

1. Which Locust version supports config files while working with realbrowserlocusts? #

You’re spot-on about Locust 0.13.5 lacking the --config flag—this feature didn’t land until Locust 1.0. The catch is that the original realbrowserlocusts package hasn’t been updated to play nice with Locust 1.x and later versions, which puts you in that tricky middle ground.

Here are your best options:

• Use a community-maintained fork: Several developers have forked realbrowserlocusts and updated it to work with newer Locust releases (including 2.x). These forks let you leverage the --config flag while still using the browser-based testing functionality you need.
• Mock config file behavior in 0.13.5: If you need to stick with the original realbrowserlocusts and Locust 0.13.5, you can replicate config file functionality with a simple Python script. Write something that reads your locust.yml settings, then translates them into the command-line arguments Locust 0.13.5 understands (like --host, --num-users, --hatch-rate) and spawns the Locust process with those args.

2. Is there a plan to update realbrowserlocusts for newer Locust versions? #

From what’s visible in the official realbrowserlocusts repo, the project has been mostly dormant since around 2020—there’s no public roadmap or announced plan to update it to support Locust 1.x or later.

That said, the community has filled the gap: active forks exist that add compatibility with modern Locust versions. If this is critical for your workflow, checking those forks (or even contributing to one) is the way to go. Alternatively, you could skip the wrapper entirely and build your own browser-based Locust tasks directly with Selenium—realbrowserlocusts is essentially a convenience layer, so rolling your own gives you full control and compatibility with newer Locust releases.

内容的提问来源于stack exchange，提问作者Michael Johnson