From: "alex_f_il@..." <alex_f_il@...>
Date: 2007-02-06T02:55:11+09:00
Subject: Re: Ajax woes

On Feb 5, 12:21 pm, Patrick Spence <patr...@pkspence.com> wrote:
> Jason Roelofs wrote:
> > There is a method on @@ie (i'm assumingWatirusage here) called
> > something
> > like #wait_for_response that will block until said execution is done.
>
> > Jason
>
> I found a #wait method, no #wait_for_response. I tried that and it
> didn't help.
>
> On one of the forms, one page of a 13-page health risk assessment,
> there's a radiobutton control associated with the question "I know my
> blood pressure". If the user clicks "Yes", then 2-more textboxes are
> displayed where they enter the systolic and diastolic readings. Without
> the "sleep()" statements, the textboxes are skippped, after logging an
> error stating that the 2-textboxes couldn't be found. The health risk
> assessment was taking about 2.5 mins to complete. With all the sleep()
> statements it's now taking about twice that long, as one would expect.
>
> --
> Posted viahttp://www.ruby-forum.com/.

I don't think it is possible with current WATIR implementation.
You can also try SWExplorerAutomation SWEA (http:\\webiussoft.com).
SWEA supports AJAX and eleminates "sleep" statements by monitoring
network traffic and DOM changes - it improves the test automation code
reliability and performance. SWEA is .Net framework, but can be used
from Ruby using RubyCLR.