inters wrote:We really like the structural commands, and they appear to be really universal. But honestly, tell us some things you can't do!
Ah, shucks, folks! Well, gee, there is always one who has to ask this.
Actually, this is quite a fair question.
It turns out that the biggest problem we see in using eValid's structural comamnds is when the underlying page is not constant. Some kinds of AJAX application pages are in continual modification, and for these it can be true that the location identified in an
IndexFindElement command is, just moments later turns out to no longer the the correct location, and subsequent commands that are base don that data won't work at all.
Think of this as a "moving target" situation. Wherever you aim, just a second later, it will be in a different place. Hard to hit things that way.
(Hmmmm, what about "leading the target" you ask? Which is kind of OK if you are skeet shooting, but won't work when you're testing a web page. At least we've never figured out how to do that deterministically!)
eValid Support Team
by inters » Tue Jul 12, 2011 3:53 pm