I've spent some time going through the release notes and checking out what HPE has in store for us in the performance space and I have to admit, it sounds like a very interesting update.
There are some key features you should be aware of in LoadRunner 12.55. I’ll unpack these in the second half of this post, but the full list of features is below:
- JMeter tests integration enables the users to run JMeter scripts from inside the Controller, alongside Vuser scripts and view JMeter test results in addition to LoadRunner measurements.
- HAR files can be generated from the Replay Summary pane (only for Web HTTP/HTML).
- Updates to correlation rules:
- Ability to search and apply correlations in HTTP headers
- Attribute based correlations (ABC): New correlation API allows dynamic value extraction from HTML documents
- Updated correlation rules (SAP Fiori, SAP NWBC, SAP WebDynpro)
- Scan using popular encoding methods (Base64/XSS encoded/decoded).
- MQTT (MQ Telemetry Transport) protocol is a M2M protocol widely used in IoT (Internet of Things). User can emulate MQTT clients and design, and execute performance testing of BQTT-based IoT systems (sensors, actuators, switches).
- TruClient scripts converted to code from actions (TruClient Web Scripts only)
- Support for Dynatrace
- Integrate Dynatrace graphs during online execution
- Opens up more metrics to be measured during a test run
- Combined reports in analysis
One of the biggest features that LoadRunner 12.55 has introduced is integration of JMeter tests, which can be run from the Controller. The added benefit is that the Controller will also be able to collect the essential JMeter tests results and can be viewed via the LoadRunner Analysis although it is very basic information.
The amount of threads will be configured in the jmx file. This means on the Controller, only one user is required from each JMeter script. Other JMeter configurations (e.g. threads, pacing, think time, etc.) should be configured through JMeter before the script is uploaded to the Controller.
Another great update in LoadRunner 12.55 is that TruClient scripts can now be converted to code from actions. This allows the user to create more complex scripts and is not restricted to only action commands. Converting the script to code mode will also reduce the memory consumption and provide a faster processing user interface compared to running it via actions.
The screenshot below shows the TruClient script in Development mode. The user then selects the Convert to Code button, highlighted in red.
The script is then converted into code mode as shown below. This is less resource intensive compared to running in action mode and will allow for more complex scripting, something that was restricted in the action mode.
Continuing on from JMeter related features, Vugen web scripts can now be converted to HAR files by replaying the script once and then selecting the Save HAR File option in the Replay Summary. The HAR files then could possibly be converted to jmx files using other third-party tools.
Vugen recording for HTTP/HTML has a nice handy feature which is available after recording. The Recording Report tab will give the option to exclude different domains from the original recording by selecting only the required domains and regenerating the script. This is a simple but great feature in removing unnecessary requests/clutter in the script.
Our team on the case
Once more users have adopted LoadRunner 12.55, we should see even more interesting uses for these new features in the real world. If you have any of your own tips and findings from LoadRunner 12.55, I’d be more than happy to hear from you. Please feel free to leave a comment on this post with your feedback or questions.