Share this page
TruClient protocols
TruClient enables you to record a variety of protocols, each suited to a particular load testing environment and resulting in a specific type of Vuser script.
Instructions for recording a script vary according to the TruClient protocol that you are using.
In this topic:
TruClient - Web protocol
TruClient - Web protocol lets you record a Web script in one of the supported browsers. For details, see Record a TruClient script.
TruClient - Mobile Web protocol
Caution: TruClient - Mobile Web protocol will be deprecated in a coming version. We recommend using TruClient - Web protocol instead.
TruClient - Mobile Web protocol lets you record mobile browser-based applications using the simulation capabilities of TruClient Browser.
For information on recording a Mobile Web script, see TruClient Mobile Web scripts and Add, Remove, and Import Mobile Device Settings for TruClient - Mobile Web in the VuGen Help Center.
TruClient - Native Mobile protocol
TruClient Native Mobile protocol provides a novel way to record and replay native mobile applications on both Android and iOS devices. It enables developers or DevOps engineers to record user interactions on mobile applications and create TruClient scripts. The protocol is designed for end-user performance testing. Together with the existing mobile protocols, it completes the LoadRunner Professional mobile performance testing suite.
TruClient - Digital Lab integration
When working with Native Mobile scripts, TruClient communicates with the Digital Lab (UFT Mobile) server, a centralized lab to which the mobile devices are connected. This enables devices to be shared between DevOps engineers and developers.
You do not need to have a mobile device with you physically. You interact with the device using a Virtual Network Computing (VNC) view inside the TruClient browser.
Digital Lab supports Android and iOS applications. Scripts that are recorded on one operating system can run on any other device from the same OS family.
Recording Native Mobile scripts
Recording a TruClient – Native Mobile script requires installation of Digital Lab.
Select the application and device on which you want to operate. The applications are uploaded to the Digital Lab server (in .apk or .ipa format). After you select an application and device, the VNC view is opened. The device is uniquely locked by you, so that no other user can interfere with your scripting. When you start recording, the application is installed on the device and launched. As you interact with it, TruClient steps are created.
For details, see Record Native Mobile scripts.
Script enhancement
Native Mobile scripts can be enhanced by using standard TruClient functionality, including parameterization, transactions, and JavaScript coding.
For details, see Use parameters to vary arguments and Work with JavaScript in TruClient scripts.
Terminology: TruClient - Native Mobile protocol vs. TruClient - Web protocol
The steps created by TruClient - Native Mobile protocol use mobile terminology such as “Tap” and “Swipe”:
The steps created by TruClient - Web protocol use web terminology such as “Click” and “Link”:
Performance analysis recommendations
You can monitor device performance measurements during the test run. These measurements include:
- CPU consumed on the device
- Free memory on the device
- Memory consumed by the application
By correlating the transaction response time and the performance measurements in the Analysis module, you can gain insight into why the application's performance suffers in certain situations.
In most environments, the back-end system is identical for all front-end systems. For example, the database and application server are serving both the web site and the mobile application. The best practice is to generate load on the back-end using a LoadRunner Professional protocol such as Web – HTTP/HTML or TruClient - Web, and at the same time, run a single user on each device you want to test, using the TruClient – Native Mobile protocol.
See also:
