I麓m using @QuarkusTest to make IT test and works fine.
Now I would like to do some StressTest, so any idea which solution it's the best fit to do this sort of testing?.
Normally I use Gatling, but it seems it does not work well with Quarkus.
Any suggestion?
Regards
@johnaohara I believe you would be the most appropriate person to shed some light on this one 馃槈
@politrons please could you describe why your Gatling test is not working with Quarkus?
It鈥檚 seems I cannot exclude JBoss log, and use logback, as Gatling need to use.
Try some options described here, but I could not make it works.
Anyway I just dedicate an hour so it might be an option, but I could not make it work yet
Please could you clarify how you are using Gatling to load test?
Gatling should be run in a separate VM from the application you are trying to test, and for reliable results a completely separate machine, there should not be any dependency conflicts between the application you are testing and Gatling as they should be completely separate processes.
Yes, I normally use in another JVM process, but for a simple POC I was trying to run the server using @QuarkusTest, but you are right it might not been a good idea.
It鈥檚 just that it鈥檚 really handy how @QuarkusTest start the application.
One more reason to not use @QuarkusTest with a load test, is that the application started in this case is not exactly the same as when starting with a typical java -jar myapp.jar where myapp.jar has been produced by mvn package.
So in effect you would not only be testing in a unrealistic environment (like @johnaohara mentions), but you would also not be testing the artifact that you would eventually (hopefully) move to production.
I would look at controlling the stress tests with a Gatling Maven or Gradle plugin, and run them as part of a build process, rather than trying to use the testing framework for something it has not been designed to do. Hope that helps
That鈥檚 what I normally do. And actually I was trying with the Gatling plugin, using the simulations, but also with the @quarkustest there as well.
You can close this ticket. I would just run the java jar generate as I normally do, and then. I will run the Gatling scenarios against that process
Most helpful comment
That鈥檚 what I normally do. And actually I was trying with the Gatling plugin, using the simulations, but also with the @quarkustest there as well.
You can close this ticket. I would just run the java jar generate as I normally do, and then. I will run the Gatling scenarios against that process