gatling-convert-from-jmeter

Convert a JMeter test plan to a Gatling simulation

Instructions

Step 1: Find input JMeter test plan

• Search for files with .jmx extension
• If several files found, ask user to specify one

Step 2: Specify output

Either find an existing Gatling project or initialize a new Gatling project:

• Try to find an existing project with the /gatling:gatling-detect-existing-project skill
• If no existing project is found, offer to create a new one with the /gatling:gatling-bootstrap-project skill

Step 3: Conversion

• Convert the JMeter test to a Gatling test written in the specified language.
• Write the output to the appropriate source directory of the Gatling project.

ThreadGroup

Each ThreadGroup converts to a scenario.

IF serialize_threadgroups true:

• Chain the scenarios with andThen ELSE:
• Just list the scenarios in the setUp block

Resource files

Files referenced in elements such as:

• CSVDataSet
• HTTPFileArgs

should be copied to the resources directory in the Gatling project.

Redirects

JMeter	Gatling
follow_redirects = true	default setting, do nothing
follow_redirects = false	disableFollowRedirect

CSVDataSet

CSVDataSet converts to a csv feeder.

IF there are several instances of CSVDataSet referencing the same file name:

• IF shareMode.group:
  • Create a new csv feeder for each scenario ELSE:
  • Create a single feeder and use it in each scenario

JMESPathExtractor

The jmesPath Gatling check extracts Strings, meaning that non String values get serialized back into JSON. Using findAll with jmesPath is a mistake, but you can tell Gatling the expected type with an extra step. Note that the check will then fail if the actual value doesn't match the expected type.

jmesPath("foo").ofString()
jmesPath("foo").ofBoolean()
jmesPath("foo").ofInt()
jmesPath("foo").ofLong()
jmesPath("foo").ofDouble()
// JSON array
jmesPath("foo").ofList()
// JSON object
jmesPath("foo").ofMap()
// anything
jmesPath("foo").ofObject()