-
Notifications
You must be signed in to change notification settings - Fork 3k
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.
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
Command line option to specify the duration to run #71
Comments
You could try the stop_timeout field in the Locust class, which is the number of seconds after which the locust will die. If it's None, it won't timeout. It will be something like this: class MyLocust(Locust):
task_set = MyTaskSet
stop_timeout = 10
... Alternatively, if you must use a command line option, you could use the -c/--clients option which specifies the number of clients to spawn and then stop. And if you can estimate how many clients are created in 'x' minutes in your test, then your good to go. |
These (here and #78 (comment)) issues are similar and or different. Should they be merged? |
Although both of us want is for the same purpose, I want it to be as a command line option so that the execution can be automated where as the other person wants it on the web page. |
Resolved in #656 |
add command for integration test and the repetition
We currently run locust tests manually with someone keeping track of the time. And we will stop the tests after 'x' minutes. We now want to automate running of locust tests in Continuous Integration server. But I dont see a command line option in locust to specify the duration to run the tests. This makes it very hard to integrate with CI server.
The text was updated successfully, but these errors were encountered: