From: Bret Pettichord <bret@...>
Date: 2007-03-21T06:37:28+09:00
Subject: Re: Ajax woes

------=_Part_144273_12641575.1174426645813
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

On 3/20/07, alex_f_il@hotmail.com <alex_f_il@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 using WATIR (run test 100 times) and
> you will see the problem. You will need to place "sleep" statements to
> make the script work stable.


Watir scripts 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 in Watir without 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 using Watir to 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

------=_Part_144273_12641575.1174426645813--