That one input field is a very strange one...instead of the
usual way or recording that, which seems to have a funny interaction
with the autocomplete feature, we will use the Index/Motion commands
to find the field and simply type in the text needed.
Below are followup items that I noted earlier...
* Here are the principles that underlie the eValid script language:
http://www.e-Valid.com/Products/Documen ... iples.html* Here is a description of how the eValid CallScript command works:
http://www.e-Valid.com/Products/Documen ... CallScript* The eValid Programmatic Interface (EPI) is described in detail in this
this introductory page:
http://www.e-Valid.com/Products/Documen ... ction.html* Here is a summary of ALL of eValid's playback synchronization modes:
http://www.e-Valid.com/Products/Documen ... mmary.html* eValid has a special capability to manipulate HTTP/S headers so
that a tester can set up unusual header combinations, including trying
special "user agent strings", as described here:
http://www.e-Valid.com/Products/Documen ... aders.html* eValid's LoadTest system imposes very realistic server load, and
we recommend use of existing performance monitoring appliances
to "close the loop" during server loading experiments. You
can see how to do for IIS and Linux servers at:
http://www.e-Valid.com/Products/Documen ... .data.html http://www.e-Valid.com/Products/Documen ... .data.html* The eValid LoadTest system has a powerful Scenario Editor that
makes the process of lifting functional tests into sophisticated
server loading scenarios involving multiple users. See the description at:
http://www.e-Valid.com/Products/Documen ... .edit.html