Objects can be identified several ways in TruClient. The recommended way is to use Automatic whenever possible. Unfortunately, this doesn’t always work. One of the best solutions is to use XPath.
Define your parameters just like you normally would for an HTTP script. Yes, the whole idea is that TruClient gets rid of correlation, but you still need to grab dynamic data from the application and use it some other place. As you may have noticed there isn’t a think time function. Instead there is a wait function. You can use it just like think time
First add a new script using the TruClient – Web protocol. To record a script, you’ll need to select what browser you want to use. On the toolbar, you’ll see a drop down next to the Develop Script button.
First, please don’t confuse TruClient with the Ajax – Click and Script protocol. These are two totally different protocols based on completely different technology. Let’s take a quick look at the history of TruClient.
For those of you who have been using LoadRunner for a while, you may have heard about the Virtual Table Server (VTS). This is a technology has been around since the early versions of LoadRunner. However, the original version of the tool was never officially supported by HPE.
Previously we looked at using DFE to help make scripts that utilize XML to make it more readable and easier to parameterize. There is another way to use DFE, beyond making a script more readable. Sometimes DFE may be required for the script to run properly. Some applications use what is called GWT (Google Web Toolkit). To use GWT DFE, first you need to identify when an application is using GWT.
DFE is short for Data Format Extension. In simple terms DFE allows for easier LoadRunner scripting by allowing us to decode and encode normally unreadable or formatted data that the may be sent between the client and the server.