This is quite possibly beyond the scope of a Gatling group, but it’s frustrating to me, since I am new to both scala and Gattling.
In my non sbt imported project, I can run the tests with a mvn clean install or mvn clean test gatling:execute but that’s all.
For debugging It’s be great not only to put breakpoints on a line of code in my .scala files and somehow turn debugging on and have it catch on these.
The plugin hooks into the first scala file directly, and that one calls all other scala files:
via <simulationClass>advanced.WebServicesJenkins</simulationClass>
and
<jvmArg>-Dgatling.defaultSimulation=advanced.WebServicesJenkins</jvmArg>
my non sbt imported project, I can run the tests with a mvn clean install or mvn clean test gatling:execute but that's all.
Is there a debug flag or something that I have to turn in in jmvArgs too?
Thanks,
Mark