Your e-Business Quality Partner eValid™ -- The Web Quality Suite
Browser-Based Client-Side Functional Testing and Validation Page Timing/Tuning Transaction Monitoring. WebSite Spidering & Analysis and Realistic Server Loading.

eValid -- IndexFindElement -- Command Description
eValid Home

The assumption here is that the "searching" within the current page. Remember, the search always begins at the current sourceIndex and results in a change to the sourceIndex only if the requested search is successful.

A Note About Perspective On A Page
UPThis means "up" on the page as seen by the viewer, i.e. toward the top of the page. This means decreasing index numbers.

The top of the page is "0".

DOWNThis means "down" on the page as seen by the viewer, i.e. toward the bottom of the page. This means increasing index numbers.

DOM Element Manipulation/Motion Commands

Working Assumptions About This Command:
  • There is only one sourceIndex known to eValid at any time.
  • The sourceIndex is always an integer.
  • The initial value of the sourceIndex is always set to zero.
  • The value of the sourceIndex persists between pages.
  • Commands that use this [internally stored] sourceIndex value always refer to the current page.
  • eValid does not modify the sourceIndex except by action of the commands below.
  • Because motion on the page is from the perspective of the view, a search DOWN toward the bottom of the page means increasing index numbers, whereas a search UP toward the top of the page means decreasing index numbers.
  • If that's not confusing enough, maybe this will help (or not): if you go all the way UP on a page, you're at sourceIndex 0.
PAGEMAP IndexFindElement wid { UP | DOWN } "property_name" ["property_value"] "frame_path"

(1) IndexFindElement wid { UP | DOWN } "property_name" "frame_path"

(2) IndexFindElement wid { UP | DOWN } "property_name" "property_value" "frame_path"

There are four variations of this command, whether to move UP or DOWN and whether to seek a name match or a name=value match.

Starting from the current sourceIndex, this command moves up or down in the DOM element index number sequence until eValid reaches the next element with a property of the specified "property_name" [or until it reaches the next element with a property of the specified "property_name" which has the specified "property_value"], or until eValid reaches the end [or beginning] of the page.

The index movement is either UP (decreasing index numbers) initial index is positive or zero. of DOWN (increasing index numbers).

When a match if found this command leaves the sourceIndex set to the index of the matching HTML element, if found. If no match is found, the sourceIndex will remain the same.

Note that if the "value" parameter is specified and is given as simply "" then this is the same as requiring that the value string for that name be empty (blank).

This is the main command. Use it to find where to take an action.

No adaptive playback activity is performed for this command.

Example Usages
Here are some typical eValid Index Motion command sequences that illustrates the process for positional navigational activity.

  # Start at the top of the page...
  IndexSet 0 
  # Here is the line in the table we want...
  IndexFindElement 0 DOWN "innerText" "UPS Next Day Air" ""
  # Now, move just a bit avoid a conflict...
  IndexMove +5
  # Here is where we want to click...
  IndexFindElement 0 DOWN "tagName" "INPUT" ""
  # Now, go ahead and click and wait for the expected navigation...
  IndexElementClick 0 "" NAV
  # Or, push the mouse down and up (this is NOT the same as a click)...
  IndexElementMouseDown 0 "" 
  IndexElementMouseUp 0 ""