{"id":1816,"date":"2014-11-28T11:17:52","date_gmt":"2014-11-28T11:17:52","guid":{"rendered":"http:\/\/blog.davidkeen.com\/?p=1816"},"modified":"2025-10-23T10:23:45","modified_gmt":"2025-10-22T23:53:45","slug":"run-multiple-gatling-simulations-with-maven","status":"publish","type":"post","link":"https:\/\/davidkeen.com\/blog\/2014\/11\/run-multiple-gatling-simulations-with-maven\/","title":{"rendered":"Run multiple Gatling simulations with Maven"},"content":{"rendered":"

Gatling<\/a> is nice load testing framework that uses Scala, Akka and Netty. It’s so much better than JMeter. It’s pretty easy to get started with scenarios written in a nice Scala DSL and it produces useful reports too. It also has a Maven plugin so you can incorporate continuous performance testing in your builds.<\/p>\n

The trouble is if you list multiple scenarios in a simulation they will all run concurrently which is probably not what you want. You need to split your tests into separate Simulation classes and run them sequentially. The plugin documentation<\/a> briefly describes a way of doing this using executions but the example is a little light.<\/p>\n

Here’s a Maven profile that when activated will run your simulations sequentially. Execute the tests with mvn test -Pperformance<\/code>.<\/p>\n