gatling-convert-from-loadrunner

Convert a LoadRunner script to a Gatling simulation

Instructions

Step 1: Find the LoadRunner script, configuration, and parameters files

• Search for LoadRunner script files:
  • Action.c, vuser_init.c, vuser_end.c: the standard three-file layout
  • Any .c or .h files in a LoadRunner script directory (look for a .usr or .lrs descriptor file nearby)
  • A single combined .c file containing all sections
• If multiple scripts or directories are found, ask the user to specify which one to convert
• Read all relevant .c and .h files before proceeding
• Read all relevant .dat files as plain text files
• Search for a default.cfg file in the same directory and read it if present
• Search for a .prm file in the same directory and read it if present

Step 2: Specify output

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

• 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 LoadRunner script to a Gatling test written in the specified language
• Write the output to the appropriate source directory of the Gatling project

Preamble

Java SDK

IF a variable needs to be saved inside the function AND the function is used within an Expression Language string:

• Move the code to an exec block that allows saving variables

When parsing dates, use java.time.format.DateTimeFormatter.ofPattern with system default zone and store it outside a function to avoid creation cost overhead.

For regular expression, use java.util.regex.Pattern.compile and store it outside a function to avoid creation cost overhead.

Gatling DSL

Be aware of DSL differences between all the languages Gatling support.

Some methods needs to be followed by .on() in Java, JavaScript and Kotlin but not Scala:

• exitBlockOnFail { ... }: exitBlockOnFail().on(...)
• group("name") { ... }: group("name").on(...)
• All loops, etc.