Ajax (Click and Script) - Replay Tips
Caution: Support for the Ajax Click & Script protocol will be discontinued in upcoming versions of LoadRunner and Performance Center.
Do not use the Ajax Click & Script protocol for new scripts.
We recommend that you migrate your existing Ajax Click & Script scripts to another Web protocol such as TruClient - Web or Web - HTTP/HTML.
This section lists tips for replaying click-and-script Vuser scripts.
Note: Some of the items below apply to specific click-and-script protocols only.
Do not change the order of the statements within a recorded script. Also, copying segments of code from one Action to another is not recommended.
If your links contain non-ASCII characters, you should instruct VuGen to convert the data to or from the UTF-8 format.
Select Replay > Runtime Settings and select the Internet Protocol > Preferences node.
Click Options to open the Advanced Options dialog box.
Locate the Convert from/to UTF-8 option and set it to Yes.
Alternatively, view the list of options that is displayed when a link is not found. Enter the displayed text as-is, such as the hex escape sequences \xA0 or any other non-standard format.
In some cases, you can perform a certain process only once—such as deleting a user from the database. Replay will fail after the first iteration because the action is no longer valid. Verify that your business process can be repeated more than once with the same data.
In the Step Navigator, double click on the previous image step to open its properties. If the Id, Name, and Alt properties are empty, provide further identification of the image, such as its file name in the Src property.
Alternatively, you can add an Ordinal argument to specify the occurrence number of the image on that page. The Ordinal argument uniquely identifies each image on the page where all other identification arguments are not unique. For more information, see the Function Reference.
If you receive a GUI Object is not found error, check the Output pane for a list of the objects in the problematic step. In some cases, the object description changes slightly from run to run.
There are several solutions:
If the new value is stable, open the script in the Editor and manually modify the value of the step's DESCRIPTION argument.
If the description changes from run to run, you can use a regular expression in the DESCRIPTION argument. For more information, see the Function Reference.
Alternatively, replace the problematic object description property, such as Name, with the Ordinal property. For more information, see the Function Reference.