eValid IndexFind vs. Xpath

[webtestgadfly]

The way you guys at eValid do the DOM processing stuff is neat, but how does your IndexFindElement command compare to using Xpath?

[eValid]

The way you guys at eValid do the DOM processing stuff is neat, but how does your IndexFindElement command compare to using Xpath?

As you know, eValid is oriented to non-programmers.

From that perspective, we think that eValid's commands are simpler and easier to use and clearer than having to use the programming-oriented XPATH
search method.

Typical eValid passages using IndexFindElement or IndexFindElementEX commands involve:

(1) Setting the starting index, e.g. SetIndex 0. Or leaving it unchanged form the last command.

(2) Issuing the IndexFindElement or IndexFindElementEX command(s) using the right parameters. In the case of the "EX" version you need to realize that you could put in a regular expression. (This is where eValid matches the XPATH type of operation).

(3) Taking an action on the page element that the IndexFind command has found.

By the way, our measurements on IndexFindElementEX show that it is much faster than XPATH, probably due to the fact that the command is executed directly in the browser rather than through interpretive JavaScript.

eValid Technical Support