MFLR - TruClient Introduction

 

Overview:

TruClient Protocol is implemented at the browser level, it can be used for testing complex web & Rich Text applications with dynamic content, which includes Mozilla Firefox and Chrome which are developed in HTML5, JavaScript, and Ajax. As well as recording and replaying all user interactions within a web application in a highly realistic way, such as clicks, keystrokes, navigation, and scrolling etc.

Difference between Web HTTP/HTML and TruClient Protocols:

TruClient Limitations:

• The TruClient API doesn't support closing dialogs opened by user code in an Evaluate JavaScript step (e.g. window.alert(“myalert ”);)
• Some TruClient scripts may fail to replay when you edit them with a higher version of LoadRunner Professional than the one you recorded them with. Ensure you backup your script before making any modifications.
• Resolution: Try running the script in the develop script mode using the latest TruClient protocol if the replay fails.
• TruClient does not record "mouse overs" if an element has a CSS rule of "Mouse Hover".
• Resolution: Click on the elements instead of hovering over them to open the dropdown menu (the clicks will be recorded).
• Java applets and Silverlight are not supported for TruClient Browser. User Actions on UI elements that are based on Java applets and Silverlight technologies are currently not supported for record and replay.
• In the default Run Block, you cannot set the mode to Random as you can in the VuGen user interface.
• Some error messages may not be localized.
• A single TruClient Vuser can utilize around 60-120 MB of memory and consume 3-30% of a single CPU (Logical Processor), depending on script complexity, web page size, and the other factors.

TruClient Best Practices:

• The script logic should be divided into multiple actions and functions, with no more than 50 steps in each action.
• The names of actions and functions should be meaningful.
• By adding comments to the script will make it easier to find specific parts of the it using the find dialog box (Ctrl + Alt + F).
• Remove unnecessary steps from the script at both Levels 1 & 2 as well, which reduces the script size, CPU & memory usage.
• It is essential that object identification is correctly configured for a successful and durable TruClient Script, so do not use default settings.
• Never use a newer version of TruClient in an older version of MF LoadRunner Enterprise or Professional.

Note: Recording, Object Identification, Transaction Names, Parameterization, Runtime Settings and Test Execution best practices will be covered in upcoming slides.