TruClient communicates with the 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.

UFT Mobile 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 a TruClient – Native Mobile script requires installation of UFT Mobile.

Select the application and device on which you want to operate. The applications are uploaded to the UFT Mobile 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 Scripts in the UFT Mobile Help Center.

Using the mobile terminology such as “Tap” and “Swipe”, the steps created by using the native mobile protocol are like the following.

Using the web terminology such as “Click” and “Link”, the steps created by using the standard web TruClient are like the following.

The 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.

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 will gain insight into why the application suffers from performance degradation under certain situations.

In most environments, the backend system is identical for all front-end systems. For example, the database and application server is serving both the web site and the mobile application. The best practice is to generate load on the backend 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.