SherryJ wrote:Hey guys, something's wrong.
I run an IndexFindElement command in eValid and my event log tells me that the element can't be found, but the PageMap says it's there.
What is the solution to this conflict of answers I am getting?
Thanks for posting your problem SherryJ.
The short answer is: Timing!
First, let's review the actual command. Here is the manual page for it: http://www.e-valid.com/Products/Documen ... ement.html
In most cases when you are looking for a simple string in a web page that is not too large, the IndexFindElement command runs very quickly.
If the page is fully loaded then you can bet that it will take 1 msec or less to find an element.
The problem comes with an AJAX page is involved, such that some parts of the page are not fully downloaded even when the page is "ready" for interaction with the user.
One solution is to introduce a simple and small delay, such as this:
IndexSet (where you want to start)
IndexFindElement (details of your command)
The Delay 100 command introduces a fixed, non-variable delay of 100 msec into the playback process.
This delay is not affected by the current setting of the Delay Time Multiplier, so it is "safe" from outside manipulation.
Usually 100 msec is more than enough time for the page to "settle down".
After that fixed delay the odds are you will find the element you're looking for.
Here for reference is an outline of ALL of the DOM manipulation commands that eValid has: http://www.e-valid.com/Products/Documen ... ation.html
In you need further help with your problem, please contact us.
-- eValid Support