You are browsing the documentation of version 3.3, go to
current documentation
Migrating from 2.3 to 3.0
Core
- JsonPath check’s
ofType
now deep converts to ScalaMap
andSeq
, so you’ll no longer get Java types deep into the object bodies
anddata
directories were dropped, now those files are resolved from classpath root, see gatling#3398.extraInfoExtractor
was dropped as it wasn’t used in any Gatling component- check’s
transformResponse
now takes a secondSession
parameter over
inject method was renamed intoduring
splitUsers
is dropped in favor ofincrementUsersPerSec
andincrementConcurrentUsers
Validation#get
is dropped as it’s very error prone, use pattern matching if you mustPerMillion
assertion is dropped asPercent
now takes a DoublegreaterThan
andlowerThan
assertion operators are renamed intogt
andlt
and are strict (vsgte
andlte
)
HTTP
- Gatling now has its own HTTP client and no longer uses AsyncHttpClient, so this library is no longer shipped. If you’ve been using it, you’ll need to pull it explicitly, or switch to another HTTP client library.
baseURL
was renamed intobaseUrl
baseURLs
was renamed intobaseUrls
and is now sticky for a given virtual usersilentURI
was renamed intosilentUri
asJSON
was renamed intoasJson
asXML
was renamed intoasXml
- WebSocket and SSE support were completely re-written, see new API.
ntmlAuth
is dropped until we can support NTLM properly, see gatling#3525- The way to compute HTTP request signatures was revamped, see new API
disableClientSharing
was dropped. It’s not possible atm to specify individual keystore and trustore for each virtual user. However, each virtual user has a distinctSSLContext
.- Debugging: in your configuration file
logback.xml
the following needs updating from:<logger name="io.gatling.http.response" level="TRACE" />
to:<logger name="io.gatling.http.engine.response" level="TRACE" />
. A full example file can be found here
JMS
reqreply
was renamed intorequestReply
matchByMessageID
was renamed intomatchByMessageId
andmatchByCorrelationID
was renamed intomatchByCorrelationId
- Protocol level
receiveTimeout
was replaced with request levelreplyTimeout
CLI
-m
/--mute
option was dropped, now Gatling is automatically mute when you set the simulation class name- no longer prompts for a user defined simulationId
gatling-maven-plugin
- Maven users must upgrade gatling-maven-plugin to 3.0.
- options’ aliases were dropped, use full option names instead
- Drop deprecated gatling-maven-plugin’s
execute
task, usetest
instead