Gatling maven plugin and executing tests.

Hey guys,
We’ve switched from just a directory with a bunch of simulations to the maven plugin for developing gatling. It’s made our lives much easier, and makes our ramp up time for development much shorter.

For ease of testing, we’d like to just create a script where we clone our git repo, install maven, then just execute the gatling scripts via maven. I’m noticing a few differences I could use a hand with though.

  1. There’s no output as the test is running. When we download gatling, we can configure our output options to have periodic reports printed out. Is it possible to do this with the maven plugin? I looked at the Mojo here

https://github.com/gatling/gatling-maven/blob/master/gatling-maven-plugin/src/main/java/io/gatling/mojo/GatlingMojo.java

but I don’t see any way to turn on this option with command line parameters.

  1. Are there any performance implications to running the simulation within the maven plugin vs the gatling distribution?

Thanks,
Todd

1) There's no output as the test is running. When we download gatling, we
can configure our output options to have periodic reports printed out. Is
it possible to do this with the maven plugin? I looked at the Mojo here

https://github.com/gatling/gatling-maven/blob/master/gatling-maven-plugin/src/main/java/io/gatling/mojo/GatlingMojo.java

but I don't see any way to turn on this option with command line
parameters.

Except if you removed the console DataWriter from gatling.conf, or if you
have something that swallows STDOUT, there's no reason for Gatling to no
print the periodic report in the console.

2) Are there any performance implications to running the simulation within
the maven plugin vs the gatling distribution?

Nope.

Thanks for the help Stéphane. I figured out my issue. I didn’t have my logging configured correctly, this was causing all of my output to be ignored, since the default log level was ERROR. I followed the instructions here.

http://gatling.io/docs/2.0.1/extensions/maven_plugin.html#override-the-logback-xml-file

And put the file logback-test.xml in the src/test/resources directory to override the defaults. Everything is working as expected now, thanks!

Todd

Great!