PaulJB wrote:Hi.
I was wondering, what happens when the eValid command that tries to search the DOM doesn't find
anything?
Is that an error?
Thanks for posting your question PaulJB.
You probably mean the search cmmands, like this:
http://www.e-valid.com/Products/Documen ... ement.htmlIn this command, if the search doesn't find a match, then the value of "sourceIndex" is left the same as it was before the command was issued.
That there is no "error code" issued is intentional...the goal of eValid scripts is to work, silently.
The presumption is that the page you are working with is constant enough so that you WILL find a match if you look for a value that you KNOW is there.
If not, the thinking is, eValid is better off not doing anything.
In concept you could detect whether "sourceIndex" changed in value by using commands like "IndexSet" and "IndexRead" and using a windows-based comparison.
Our experience is that this very seldom useful.
-- eValid Support