* Modal dialogs present a special problem for eValid because, being
"modal" eValid can't get control to make a recording. Here are some
hints about how to handle modal dialogs:
http://www.e-Valid.com/Products/Documen ... hints.html http://www.e-Valid.com/Products/Support ... login.html* eValid has ~60 switches that control executions from the Windows command
line, described here:
http://www.e-Valid.com/Products/Documen ... rface.html* For scheduling eValid actions (e.g. for monitoring) the best solution is
to use the powerful Windows scheduling system, as described here:
http://www.e-Valid.com/Products/Documen ... duler.html* Here is the complete description of eValid's Validation modes:
http://www.e-Valid.com/Products/Documen ... ation.html* eValid, during playback, has ERROR, WARNING, ALARM and TIMEOUT flags that
can be used to adjust the flow of control as described here:
http://www.e-Valid.com/Products/Documen ... rting.html http://www.e-Valid.com/Products/Documen ... .html#flag * If you wish to -- and for AJAX like applications this capability may
be NECESSARY to maintain playback synchronizations -- you can validate
and synchronize on ANY element [or element property value] in the page,
using:
http://www.e-Valid.com/Products/Documen ... n.dom.html* The eValid PageMap facility -- which reveals the contents of the
current page eValid is showing you -- gives you a direct look into
the document object model (DOM) of the page. Here's how to use it:
http://www.e-Valid.com/Products/Documen ... p.gui.html