Small correction: Watir keeps references to the element proxies. The
DOM elements are located in the IE process. Every check for the
element availability is marshalled between the processes (test script
and IE).
-Alex
···
On Mar 23, 11:19 am, "Bret Pettichord" <bpettich...@gmail.com> wrote:
On 3/20/07, alex_f...@hotmail.com <alex_f...@hotmail.com> wrote:
SWEA doesn't block the browser - it could be a very bad idea to
block
the browser. SWEA monitors all Browser activity in real-time and
is
able correctly rebind (reidentify) SWEA controls in the case of
the
changes. It makes automation script more reliable and stable. Try
to
automate any complex AJAX grid usingWATIR(run test 100 times)
and
you will see the problem. You will need to place "sleep"
statements to
make the script work stable.Watirscripts don't need to rebind then there are changes.Watir
objects reference elements of the DOM and these references are stable
until the element no longer exists or a new page is loaded.I have run many complex scripts multiple times inWatirwithout
problem. What kinds of problems are you seeing? Are the scripts
slowing down? Are you getting intermittent failures? Memory leaks? It
sounds scary when you say it is not stable or reliable, but I'm not
getting a clear picture of what this looks like to you.As mentioned earlier in the thread, people usingWatirto test Ajax
typically use the "wait_until" method to avoid sleep statements. I
would like to see an example where this wasn't an option. I agree:
sleeps should be avoided.Bret