RealBrowser Protocol

What is RealBrowser Protocol?

On a classic protocol user path, NeoLoad dialogs with remote servers using HTTP requests and responses. However, due to the dynamic nature of some web applications, these HTTP requests can require a lot of variabilization work to be replayable at scale.

With the RealBrowser feature, NeoLoad records interactions on the browser and replays them, just like a real user does. It is the browser that handles sending the subsequent HTTP requests. Meaning, RealBrowser scenarios become a framework and implementation agnostic and the complexities of different websites technologies are abstracted.

Supported NeoLoad versions

RealBrowser is available on:

• NeoLoad (GUI, Controller, LG) from version 9.0.0
• NeoLoad Web from version 4.0.0

Supported OS platforms

Docker image for RealBrowser LG is available at: docker pull neotys/neoload-loadgenerator:real-browser-latest.

You need an internet connection to run a Browser Based record or scenario in macOS in Beta Version. The first launch can take up to a minute. This is required for downloading the browser in a background process.

Supported Browsers

NeoLoad RealBrowser protocol covers the most commonly used browsers.

At record time:

• Windows 64 bits

At runtime:

• Chromium (by default)
• Firefox (bundeled with Neoload)
• WebKit (bundled with NeoLoad)
• Google Chrome (requires a local installation of Google Chrome)
• Edge (requires a local installation of Edge)

Select the browser you want to use in the OpenBrowser action.

Browser versions

NeoLoad includes the latest browser versions with each new release.

You have the option to specify a path to an arbitrary (non-bundled) browser of your environment. However, there is no guarantee that this option will work and that issues will not arise - use with caution.