Changes and Improvements to LoadRunner 2020

LoadRunner logo

There are many changes and improvements in the LoadRunner 2020 release. These changes may affect how you use the tool, so it’s important to be aware and adapt your processes accordingly.

 

This blog will address the most significant changes, including:

  • Name Changes
  • Installation
  • Community License Change
  • New Look
  • DevWeb Protocol
  • TruClient Protocol

 

Name Changes for the LoadRunner Family of Products

  • “LoadRunner” was renamed to “LoadRunner Professional 2020”

        LoadRunner Graphic

 

  • “Performance Center” was renamed to “LoadRunner Enterprise 2020”

           LoadRunner Performance Center Icon         

 

  • “StormRunner” was renamed to “LoadRunner Cloud 2020”

                 StormRunner Icon

 

Installation

.Net Framework 4.8 is now a requirement to install LoadRunner. This may affect what machines you install LoadRunner on, especially if the machine has other products installed that do not work with the latest .net framework version. Despite what the installation says, you can pick “LoadRunner Enterprise” if you want the Load Generator to run as a service for LoadRunner Professional.

 

LoadRunner Installation

 

Community License Change

The LoadRunner Community License is now installed automatically, unlike LoadRunner 12.6x which required a separate request and license installation to be done. This means you can use LoadRunner immediately after the installation completes.

LoadRunner Community License

 

 

New Look

LoadRunner 2020 now has a dashboard-look for easy analysis, similar to most modern tools. All the same information is present in this release as was in previous LoadRunner versions.

The screenshot below shows the Analysis tool in Windows, although the web report has the same look.

 

LoadRunner Analysis Tool

 

 

DevWeb Protocol

This release is the first version of LoadRunner that fully supports DevWeb. The previous version was beta support. Standalone Devweb is cross platform (Windows, Mac, and Linux), and DevWeb has functionally added to be similar to HTTP Web/HTML.

Measured performance is also very similar (comparison below):

DevWeb Protocol

Developers can create DevWeb scripts in their Integrated Development environment (IDE), which most may be more familiar with instead of having to learn a new tool like LoadRunner. Supported IDE’s include Visual Studio Code, Atom.io, JetBrains WebStorm (IntelliJ), and many more.

A user can run 150 free virtual users with DevWeb Standalone and 50 free concurrent users with this version of LoadRunner.

 

 

TruClient Protocol

TruClient Lite, a Chrome browser plug-in, is no longer supported, and LoadRunner 2020 cannot read these scripts. You need to use LoadRunner 2020 or TruClient Standalone, both of which have the same functionality.

This release of LoadRunner includes updated browser support. TheTruClient browser is now equivalent to Mozilla 65.0.3, and theChromium browser is now at Chromium 76.

Three new metrics are available in Analysis of tests:

TruClient Protocol

These new measurements allow two tests to be ran at once, saving time. You can run a TruClient test, then subtract the DOM Interactive to get the Web HTTP/HTML measurement.

 

At last week’s MicroFocus Universe conference, exciting changes were stated in the upcoming release for the LoadRunner family of products.

Once these changes are officially released and used, look forward to an updated blog post to share that information.

 

Olenick has significant experience using all versions of LoadRunner for all types of Performance Testing.

Get in touch with us to discuss how Olenick can assist your business with Performance Testing using LoadRunner.

 

Mike Willett Headshot

Mike Willett