Locust: Provide a max timelimit for web ui initiated test runs

[reedstrm]

Need a safety backstop for web UI initiated performance tests

I've just started working with locust, but already have walked away for meetings twice, and left my poor dev instance being hammered with tests-under-development. Appreciate the CLI time limit feature. Would the devs be open to a PR that implements a configurable time limit from the web ui as well?

[reedstrm]

As a work around I've found and been setting max_timestop on my HttpLocust classes. This does at least stop the hammering, but the test itself doesn't stop (even though there's 0 users left running, and reported so in the GUI)

[cgoldberg]

Would the devs be open to a PR that implements a
configurable time limit from the web ui as well?

+1

[cyberw]

@reedstrm Lots of +1 :) Will you have a look?

[reedstrm]

Sure - as it happens, my local load test frame work just came back to the front burner at work, so I can legitimize the time. :-)

[cyberw]

@reedstrm any progress? :)

[cyberw]

Closing due to lack of activity. I’m not saying it is a bad idea, just that it is unlikely to be prioritiezed.