Closed 8altazar closed 5 years ago
Because the locust master exits. What do you need?
Eg. add some field in Locust.java private boolean exitEnabled;
with default value true and method with possibilty to change it. What do you think about it?
It's not necessary, what do you want to do if it doesn't exit?
Read locust csv results, do some asseration and generate report junit/allure. All with one command mvn test
.
What about put all the code into another tool? Or you can add a shutdown hook by calling Runtime.getRuntime().addShutdownHook()
Yes, i have to find some workaround.
If you use locust4j as a plugin in maven, calling System.exit() may exit maven itself. But maven is not a suitable environment to run locust4j, jenkins may be better.
I would like to do full automated performance test with csv results analysis (asseration) in java and report generated for example in allure tool. Problem is: after load testing (locust --run-time reached) in Runner.java (line 228)
System.exit(0)
is called.