Gatling 3.0.0-RC1 is out!

Hey there,

We are very excited to announce that the first Release Candidate of Gatling 3.0 is finally out!

Gatling 3.0 is the result of a 2 years long effort in internals refactoring and new features implementation such as:

  • Java 9/10/11 support
  • new internal HTTP client
  • HTTP/2 support
  • new WebSocket support

Please check the documentation for new features and how to migrate.

We plan on having frequent new release candidates for one month top, so we’re very eager to get your feedback!

Cheers,

Hi, guys! Great work!

extraInfoExtractor was dropped as it wasn’t used in any Gatling component

https://gatling.io/docs/current/migration_guides/2.3-to-3.0/#to-3-0

Any alternative for this?

extraInfoExtractor was dropped as it wasn’t used in any Gatling component

https://gatling.io/docs/current/migration_guides/2.3-to-3.0/#to-3-0

Any alternative for this?

Well, it depends on what you were doing with this.

Stéphane Landelle

GatlingCorp CEO
slandelle@gatling.io

extraInfoExtractor was dropped as it wasn’t used in any Gatling component

https://gatling.io/docs/current/migration_guides/2.3-to-3.0/#to-3-0

Any alternative for this?

Well, it depends on what you were doing with this.

We develop own report tool and we parse simulation.log now. And via extraInfoExtractor we provide to simulation.log additional information such as response HTTP status code, request URL and body per request/row.

extraInfoExtractor was dropped as it wasn’t used in any Gatling component

https://gatling.io/docs/current/migration_guides/2.3-to-3.0/#to-3-0

Any alternative for this?

Well, it depends on what you were doing with this.

We develop own report tool and we parse simulation.log now. And via extraInfoExtractor we provide to simulation.log additional information such as response HTTP status code, request URL and body per request/row.

How many cost keep this feature in Gatling 3? It’s great way to enrichments simulation.log for Gatling users.

We develop own report tool and we parse simulation.log now.

Unsupported usage then.

How many cost keep this feature in Gatling 3? It’s great way to enrichments simulation.log for Gatling users.

extraInfoExtractor won’t come back. It was intended for debugging and we repeated countless times that simulation.log was an implementation detail that was only used from our HTMT reports engine. We dropped it for very good reason: it was causing many issues with people dumping large content in there, the proper was for debugging is to lower logging level, and we’re considering making many serious changes with the file format, such as going with a binary format instead of clear text.

Thank you for this long-expected release!

But I have the only question:

Could you please advise on replacement for splitUsers strategy?

I utilized it for scenario where I needed consecutive load jumps during expected load run.

For example:

class GatlingSimulation extends Simulation {
  setUp(
    GatlingScenarios.testScenario.inject(
      splitUsers(105000) into(constantUsersPerSec(15) during(200)) separatedBy(
        constantUsersPerSec(600) during(30))))
    .maxDuration(30 minutes)
    .protocols(testAPI.httpConf.disableCaching)
}
Iterator.continually(Seq(constantUsersPerSec(15) during(200), constantUsersPerSec(600) during(30))).flatten.take(30 * 60 / 230).toSeq