Use the mouse and not the keyboard
It is preferable to click on an object with the mouse rather then using the
keyboard. During recording, use only GUI objects that are within the
browser's pane. Do not use any browser icons, controls, the Stop button, or
menu items, such as View > Refresh. You may, however, use the Refresh,
Home, Back and Forward buttons and the address bar.
Do not record over an existing script
It is best to record into a newly created script—not an existing one.
Avoid context menus
Avoid using context menus during recording. Context menus are menus
which pop up when clicking an item in a graphical user interface, such as
right-click menus.
Avoid working in another browser while recording
During recording, do not work in any browser window other than the
browser windows opened by VuGen.
Wait for downloads
Wait for all downloads to complete before doing any action, such as clicking
on a button or filling in a text field.
Wait for pages to load
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.
Navigate to start page
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 at the end of your recording, so that the same link
will be visible at the end of the business process.
Use a higher event configuration level
Record the business process again the High Event Configuration level.
Disable socket level recording
In certain cases, the capturing of the socket level messages disrupts the
application. For most recordings, socket level data is not required. To
prevent the recording of socket level data, disable the option in the
recording options. For more information, see the section about recording
with Click and Script.
Enable the record rendering-related property values
If the client-side scripts of the application use a lot of styling activities,
enable the Record rendering-related property values option before
recording the script. For example, enable this option to record additional
DOM properties such as offsetTop. Note that enabling this option may
decrease the recording speed. You can enable the Recording Options > GUI
Properties > Advanced node
Replay Tips
The following section lists tips for replaying click and script scripts.
Do not reorder
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.
Convert non-ASCII characters
If your links contain non-ASCII characters, you should instruct VuGen to
convert the data to or from the UTF-8 format.
To enable UTF-8 conversion:
➤ Open the Recording Options. Select Vuser > Run-Time 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 alternatives that are 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.
Run same sequence of actions twice
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 in no longer valid. Verify that your business process can be repeated
in the application more than once with the same data, without recording.
Set unique image properties
In Tree view, 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 Online Function Reference
(Help > Function Reference).
Check the step’s description
If you receive an error GUI Object is not found, check the Replay Log in the
Output window, 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.
➤ If the description changes from run to run, you can use a regular
expression in the DESCRIPTION argument. For more information, see the
Online Function Reference (Help > Function Reference).
➤ Alternatively, replace the problematic object description property, such as
Name, with the Ordinal property For more information, see the Online
Function Reference (Help > Function Reference).
Miscellaneous Tips
The following additional tips may help you in troubleshooting your
problems:
Search for warnings
Search for warnings or alerts in the Replay Log.
Verify the response
Verify the response of the previous step is correct using web_reg_find. For
more information, see the Online Function Reference (Help > Function
Reference).
Use alternate navigation
For problematic steps or those using Java applets, Use Alternative
Navigation to replace the Web (Click and Script) step with an HTTP level
step. Note that the HTTP level steps may require manual correlations. To
perform Alternative Navigation, select a step in Tree View, or the text in
Script View, and select Replace with alternative navigation from the
right-click menu.
Working with the Kerberos Protocol
If you are using the Kerberos Protocol for authentication, you must
customize VuGen to properly convene authorization sessions. Advanced
users can attempt to perform this customization themselves.
In order for the Kerberos Protocol to work properly, create a krb5.ini file and
put it in an available directory. Save the full path name of krb5.ini into the
KRB5_CONFIG environment variable.
The krb5.ini file should contain detailed information about each domain
(KDS and AS addresses) and trust chains.
For more information, contact HP software support.
It is preferable to click on an object with the mouse rather then using the
keyboard. During recording, use only GUI objects that are within the
browser's pane. Do not use any browser icons, controls, the Stop button, or
menu items, such as View > Refresh. You may, however, use the Refresh,
Home, Back and Forward buttons and the address bar.
Do not record over an existing script
It is best to record into a newly created script—not an existing one.
Avoid context menus
Avoid using context menus during recording. Context menus are menus
which pop up when clicking an item in a graphical user interface, such as
right-click menus.
Avoid working in another browser while recording
During recording, do not work in any browser window other than the
browser windows opened by VuGen.
Wait for downloads
Wait for all downloads to complete before doing any action, such as clicking
on a button or filling in a text field.
Wait for pages to load
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.
Navigate to start page
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 at the end of your recording, so that the same link
will be visible at the end of the business process.
Use a higher event configuration level
Record the business process again the High Event Configuration level.
Disable socket level recording
In certain cases, the capturing of the socket level messages disrupts the
application. For most recordings, socket level data is not required. To
prevent the recording of socket level data, disable the option in the
recording options. For more information, see the section about recording
with Click and Script.
Enable the record rendering-related property values
If the client-side scripts of the application use a lot of styling activities,
enable the Record rendering-related property values option before
recording the script. For example, enable this option to record additional
DOM properties such as offsetTop. Note that enabling this option may
decrease the recording speed. You can enable the Recording Options > GUI
Properties > Advanced node
Replay Tips
The following section lists tips for replaying click and script scripts.
Do not reorder
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.
Convert non-ASCII characters
If your links contain non-ASCII characters, you should instruct VuGen to
convert the data to or from the UTF-8 format.
To enable UTF-8 conversion:
➤ Open the Recording Options. Select Vuser > Run-Time 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 alternatives that are 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.
Run same sequence of actions twice
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 in no longer valid. Verify that your business process can be repeated
in the application more than once with the same data, without recording.
Set unique image properties
In Tree view, 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 Online Function Reference
(Help > Function Reference).
Check the step’s description
If you receive an error GUI Object is not found, check the Replay Log in the
Output window, 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.
➤ If the description changes from run to run, you can use a regular
expression in the DESCRIPTION argument. For more information, see the
Online Function Reference (Help > Function Reference).
➤ Alternatively, replace the problematic object description property, such as
Name, with the Ordinal property For more information, see the Online
Function Reference (Help > Function Reference).
Miscellaneous Tips
The following additional tips may help you in troubleshooting your
problems:
Search for warnings
Search for warnings or alerts in the Replay Log.
Verify the response
Verify the response of the previous step is correct using web_reg_find. For
more information, see the Online Function Reference (Help > Function
Reference).
Use alternate navigation
For problematic steps or those using Java applets, Use Alternative
Navigation to replace the Web (Click and Script) step with an HTTP level
step. Note that the HTTP level steps may require manual correlations. To
perform Alternative Navigation, select a step in Tree View, or the text in
Script View, and select Replace with alternative navigation from the
right-click menu.
Working with the Kerberos Protocol
If you are using the Kerberos Protocol for authentication, you must
customize VuGen to properly convene authorization sessions. Advanced
users can attempt to perform this customization themselves.
In order for the Kerberos Protocol to work properly, create a krb5.ini file and
put it in an available directory. Save the full path name of krb5.ini into the
KRB5_CONFIG environment variable.
The krb5.ini file should contain detailed information about each domain
(KDS and AS addresses) and trust chains.
For more information, contact HP software support.
No comments:
Post a Comment