Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

clarifying locust class usage when no classes specified on CLI #925

Merged
merged 1 commit into from Dec 4, 2018
Merged

clarifying locust class usage when no classes specified on CLI #925

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
4 changes: 3 additions & 1 deletion docs/writing-a-locustfile.rst
View file
Open in desktop
Expand Up @@ -48,7 +48,9 @@ The *min_wait* and *max_wait* attributes can also be overridden in a TaskSet cla
The *weight* attribute
----------------------

You can run two locusts from the same file like so:
If more than one locust class exists in the file, and no locusts are specified on the command line,
each new spawn will choose randomly from the existing locusts. Otherwise, you can specify which locusts
to use from the same file like so:

.. code-block:: console

Expand Down