Migrating from 2.0.0-M3a to 2.0
Gatling requires at least JDK7u6
As targeting newer JDKs provides bug fixes, speed improvements and opens opportunities for optimization, Gatling now requires at least a JDK7u6 (released almost two years ago already).
Gatling is now available on Maven Central
Gatling releases are now available on Maven Central, and snapshots are deployed on each successful build by Travis CI to Sonatype’s snapshots repository.
If you were using Gatling with its Maven plugin, you no longer need to add the Excilys repository in your
import assertions._are now unnecessary and have to be removed.
import io.gatling.http.Headers.Names._is now unnecessary, headers names are now directly available from
import io.gatling.http.Headers.Values._is now unnecessary, headers values are now directly available from
exitASAP now defaults to true. For more information on the change of behaviour it introduces, see asLongAs documentation.
whateverhas been renamed to
transformnow no longer takes and returns an
Option[T]and takes and returns plain types, but
transformOptionprovides the same functionality as
Form parameters (for POST requests)
Methods for adding form parameters to the request have been renamed:
responseInfoExtractorhave been merged into a single
extraInfoExtractor, which takes a
ExtraInfo => List[Any]function.
gatling.http.ahc.useRawUrlconfiguration parameter was removed, please use
disableUrlEncodinginstead, as described here.
For more information on
extraInfoExtractor, please refer to its documentation.
simulation.log has been redesigned.
If you wrote your own specific
simulation.log parser, you’ll need to migrate it to the new structure.
Until now, when setting up the Recorder, you had to setup two ports for the Recorder’s local proxy: one for HTTP, one for HTTPS. This is not needed anymore, as the Recorder handles itself the switch to an HTTPS connection if necessary, and only a single port needs to be specified.
<excludes>...</excludes> configuration options have been removed.
Should you want to select a specific simulation to run, you can use the
<simulationClass>...</simulationClass> config option to do so.
For more information, see the Maven plugin documentation.