Known issues for Click & Script protocols

This section describes troubleshooting and limitations for click & script protocols.

Note: Some of the items below apply to specific click & script protocols only.

GUI object not found

Does the error occur at the beginning of the second iteration?

If the error occurs at the beginning of the second iteration's Action section, it is probably the result of a starting page that was present for the first iteration, but missing for the second one. If the last page in an action does not contain the links and buttons that were available at the start of the iteration, then the next iteration will fail. For example, if the first page has a text link Book A Flight, make sure to navigate to the appropriate page, so that the same link will be visible at the end of the business process.

Is it a text link containing non-ASCII characters?

If the problem occurs with non-ASCII characters, you should instruct VuGen to covert the data to a suitable character set.

  1. Select Replay > Runtime Settings and select the Internet Protocol > Preferences node.

  2. Click Options to open the Advanced Options dialog box.

  3. Locate Charset Conversions by HTTP in the Web (Click & Script) > General options, and set it to Yes.

Enable UTF-8 conversion for Linux Machines

  1. Select Replay > Runtime Settings and select the Internet Protocol > Preferences node.
  2. Click Options to open the Advanced Options dialog box.
  3. Locate Convert from/to UTF-8 in the General options and set it to Yes

Alternatively, view the list of alternatives that are displayed when a link is not found. Enter the displayed text as-is, such as hex escape sequences \xA0 or any other non-standard format.

Can you run the same sequence of actions twice in the application?

In some cases, you can only perform a certain process 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 in the application more than once with the same data, without recording again.

Were the image properties 'Id', 'Name' and 'Alt' empty?

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

Did the step's description change?

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 View and manually modify the value of the step's DESCRIPTION argument(s).

  • If the description changes from run to run, you can use a regular expression in the DESCRIPTION argument(s). 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.

Did the page load completely during recording?

During recording, it is best to wait for the page to load completely before doing the next step. If you did not wait for all of the pages to load, record the script again.

Replay failure

If the replay is failing at a particular step, check the step description. VuGen sometimes reads a single space as a double space. Make sure that there are no incorrect double spaces in the string.

Out of memory error in JavaScript

Increase the JavaScript memory in the Runtime settings.

  1. Select Replay > Runtime Settings and select the Internet Protocol > Preferences node.
  2. Click Options to open the Advanced Options dialog box.
  3. Locate the Memory Management JavaScript Runtime Memory Size (Kb) and Memory Management JavaScript Stack Memory Size (Kb) options.
  4. Increase the memory sizes to 512Kb or higher.

    5. VuGen displays JavaScript errors

    If VuGen displays JavaScript errors in the Output pane, enable IE (Internet Explorer) script errors in order to verify that the Javascript itself does not contain errors.

  1. Open Internet Explorer.

  2. Select Tools > Internet Options and click the Advanced tab.

  3. Under Browsing, select the Display a notification about every script error check box.

  4. Rerun the application in IE. If IE displays script errors, then there is a problem with the JavaScript application. If it is not possible to fix the application, you can safely ignore the corresponding replay errors.

    5. Problems following parameterization

    If you encounter problems only after you have parameterized values, verify that the values are valid for your application. Perform business process with the value of the parameter and verify that the application accepts it.

    Problems with applications that utilize styling actions

    If the client-side scripts of the application use a lot of styling activities, you should record the script again after enabling the Record rendering-related property values option. This enables the recording of additional DOM objects.

  1. Select Recording > Recording Options and select the GUI Properties > Advanced node.
  2. Select the Record rendering-related property values check box.

Re-record the Vuser script.