Run the tests for the specified time

[diegows]

I think it would be great to have an option to define how many time we want to run the tests from the web interface.

[aztlan2k]

I agree. It's possible to stop the test run using the command line --num-request=N option, but i also think it would be great to have options for stopping after a specified number of tasks have been executed and after a specified time has elapsed.

--num-tasks=N         stop after N tasks have been executed.
--run-time=N[smh]    stop after the specified amount of time, e.g. (300s, 20m, 3h)

Making these available via the web UI would be very useful as well.

[diegows]

I've been thinking in a workaround in the meantime, may be we can use on_start() method to schedulie the call to the interrupt() method after some time. I have tested it, what do you think?

[livfc]

I got round this by creating ant targets which start and stop the spawn using the same APIs as the web interface. In between the start / stop, the sleep function is called based on an ant variable. A Jenkins job requests all the parameters and passes to the ant script.

[Jahaja]

I agree. This would be useful.

[garrettheel]

+1 @aztlan2k

I'm currently using stop_timeout on my Locust to achieve this but I'd prefer to be able to pass in the value as an arg instead of hardcoding it in the locustfile.

[jeffandersen]

+1, have implemented it with interrupt as a workaround for now. Would be nice to be native.

[heyman]

Fixed by #656!