title | description | lead | date | lastmod | weight |
---|---|---|---|---|---|
Migrating from 3.3 to 3.4 |
Gatling migration from 3.3 to 3.4 |
2021-04-20 18:30:56 +0200 |
2021-04-20 18:30:56 +0200 |
1040 |
{{< alert warning >}}
There's a know issue with headerRegex
that forces you to force the parameter to a String
when using the predefined HTTP header names constants, eg header(HttpHeaderNames.ContentType.toString, "bar")
.
Sadly, this is something we'll only be able to fix in Gatling 3.5.0.
{{< /alert >}}
{{< alert tip >}} Gatling 3.4 is not binary compatible with previous versions. Any code compiled with a previous version must be recompiled in order to be executed with Gatling 3.4. Changes listed below are only about source compatibility changes. {{< /alert >}}
- the Session based versions of
transform
andtransformOption
were renamed intotransformWithSession
andtransformOptionWithSession
. xpath
check's namespaces are now aMap[String, String]
instead of aList[(String, String)]
- Configuration option in
gatling.config
related to ssl, sockets, and netty were moved around in an effort to share amongst multiple protocol supports, eg MQTT (FrontLine).
hostNameAliases
now takes aMap[String, List[String]]
instead of aMap[String, String]
HttpHeaderNames
andHttpHeaderValues
are deprecated and planned for removal in the next release. Useio.netty.handler.codec.http.HttpHeaderNames
andio.netty.handler.codec.http.HttpHeaderValues
instead.