Convert LoadRunner or SOAPUI to open-source with ShiftLeft Converter

The free ShiftLeft Script Converter can convert LoadRunner HTTP to JMeter and LoadRunner TruClient to Selenium in a short time, as well as SOAPUI scenario(s) to Taurus and BlazeMeter.

For more information about converting scripts to Selenium, see Convert LoadRunner to Open-Source Selenium in Minutes.

Choose location and output format

Before you start a conversion, choose where the converted test will be created in BlazeMeter and which output format you want for the converted script.

In the Upload script step, you now choose:

  • Where the converted test will be created in BlazeMeter.

  • Which output format you want for the converted script.

Choose a test location

Before starting the conversion, choose an Account, Workspace, and Project.

How it behaves:

  • If you are not logged in, the location fields stay disabled and show Login required.

  • When you change the Account, the Workspace list updates automatically.

  • When you change the Workspace, the Project list updates automatically.

Smart defaults

To save time, the converter remembers your choices:

  • If you used the converter before, your last selected Account, Workspace, and Project are preselected.

  • If not, the converter uses your default BlazeMeter project location.

Choose output format

You can choose one output format before the conversion starts:

  • JMX

  • YAML

How it behaves:

  • Output format must be selected before conversion starts.

  • Your selected format is saved as your preference when you are logged in.

What you see in results

After conversion:

  • If JMX output is available, you see Download JMX.

  • Otherwise, you see View YAML File.

For AI enhancement, if JMX was selected but a valid JMX file could not be generated, AI enhancement is not available for that result.

If location access does not match your account or workspace permissions, conversion can be blocked.

Some script types may not support JMX as the primary output, and the converter may continue using the YAML flow instead.

Convert to JMeter

You can convert the tests assuming only HTTP(S) protocols (and derivatives). In LoadRunner terms, these are:

  • Web - HTTP/HTML

  • Web Services

  • RTE

  • Winsock

  • MQ

  • JMS

  • Soap

Prerequisites:

  • You have JMeter installed.

Follow these steps:

  1. Go to https://shiftleft.blazemeter.com and upload the ZIP file.
  2. Open the test in BlazeMeter and download the zip file that contains all converted assets.
  3. Open the downloaded file, and open the folder named “Your JMeter or Selenium Scripts”.
  4. Copy the JMX file to a folder on your computer.
  5. Open the JMX file in JMeter, and adjust the script if you needed, and run it.

Convert to Taurus

With the Script Converter, you can convert your tests to Taurus, an open-source automation framework. Taurus allows you to run and automate open-source tests and view analytics. For more information about Taurus, see gettaurus.org.

Prerequisites:

  • You have JMeter installed.

Follow these steps:

  1. Go to https://shiftleft.blazemeter.com and upload the ZIP file.

  2. Open the test in BlazeMeter and download the zip file that contains all converted assets.
  3. Copy the YML and .TXT files, and put these in the same folder in your computer. Adjust the YML file in your Text editor of choice, if needed.
  4. Install Taurus if necessary.
  5. Run the command
    $ bzt <your_filename.yml>
  6. View and analyze the results.

You just ran your LoadRunner file in Taurus.

Convert to BlazeMeter

Prerequisites:

  • You have JMeter installed.

You can convert LoadRunner scripts to BlazeMeter.

  1. Go to https://shiftleft.blazemeter.com and upload the ZIP file.
  2. Open the test in BlazeMeter and download the zip file that contains all converted assets.
  3. Configure your tests from the converted ZIP file, either:
    1. Extract the JMX and create a JMeter test; OR
    2. Extract the YML and create a Taurus test.
  4. In BlazeMeter, the “Test History” tab displays various details such as the Test execution engine is used, the number of Concurrent Users/Threads, and the available Locations and providers (AWS, Google, Azure) from where the tests can be executed.

  5. Launch the test for the default duration of 20 mins.

You can now view the test results on BlazeMeter.

Supported files and functions (LoadRunner HTTP and TruClient)

See a list of supported files and functions (LoadRunner HTTP and TruClient)

Resolve errors

For issues with the new location and output format options:

  • Location list is empty - Make sure you are logged in and have access to at least one Account, Workspace, and Project.

  • Selected location is rejected - The selected Workspace may not belong to the selected Account in your current BlazeMeter access scope.

  • You selected JMX but still see YAML-related behavior - For some unsupported scenarios, fallback to YAML is expected.

  • AI option is not available after selecting JMX - AI enhancement requires a valid generated JMX file.