Summary
This page describes the common problems encountered with
eValid license installation and operation.
Breakpoint Command
The Breakpoint command puts the eValid playback engine in "Pause" mode.
In troubleshooting it is good practice to put this command in just before the area
where you are experiencing difficulty.
From that point forward you can either single-step (see below) or resume playback.
Single-Step Command
At any point in script playback you can pause eValid and then advance one command at
a time in "single step" mode.
It is often very valuable to see what happens after each command is completed.
Forced De-Synchronization
When a playback experiences de-synchronization it is often valuable to
force de-synchronization by adjusting the Wait Time Multiplier, or putting
ceilings or floors on wait times that occur in the script.
If there is a synchronization or timing problem this technique will
amplify it so that an appropriate synchronization step can be added to the script.
Suppress Adaptive Playback
Adaptive playback resolves page ambiguity as the result of small changes to the page.
In some cases, the action of the adaptive playback feature can mask properties
of the playback that are dangerous to other parts of playback.
The Adaptive OFF and Adaptive ON commands can be used to toggle
this feature OFF/ON.
PageMap Structural Investigation
Use of the PageMap during script playback sometimes involves some unwanted
overhead, but in some cases having the PageMap active will reveal features or
properties of a playback that would not otherwise be noticed.
Insert Recording
In many case, once a script problem has been identified, it is easiest to
us the Insert Recording feature to add commands in the middle of the script,
including [perhaps] some that may eventually be removed.
Observe EventLog
The EventLog message area provides very good information about the outcome of
a command and in particular when used with Single-Step mode you can readily see
what is happening (and what is NOT happening) on the page based on the user
actions specified in the test script.
Hover Time Analysis
For page areas that are supported by JavaScript it may be important to hover
over an element until the state changes to "active"
(usually indicated by a change in the background color).
Study of the EventLog simultaneously is also often helpful.
Locate Critical Page Elements
In some cases, it is valuable to use the
IndexFindElement
command
to locate where a particular feature -- a text item, an image, a table cell, etc. --
is found on the page.
You add the command to the script followed by a breakpoint, and then study the
eventlog messages that will report the success (or failure) of the command.
In rare cases you may need also to use the
IndexFindElementEX
command, which is slower but which searches the page for regular-expression (R.E.)
matches.
Specific Troubleshooting Topics
Here are additional troubleshooting pages that pertain
to specific types of problems:
