Regards,
Simon
> --
> You received this message because you are subscribed to the Google Groups "webdriver" group.
> To post to this group, send email to webd...@googlegroups.com.
> To unsubscribe from this group, send email to webdriver+...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/webdriver?hl=en.
>
>
Simon
Fortunately, you, as the app author, know how to check that the page
is loaded. One popular approach I've seen to this is what I like to
think of as the "Eternal Optimist" pattern: rather than limiting page
loaded checks to a set duration or number of retries, the wait class
continues checking indefinitely, relying on an external controller
(such as a continuous build server) to kill the test if it takes too
long.
Simon
Which is a long way of saying that even if we exposed all the bells
and whistles, you'd still not get consistent behaviour, and you'd
_still_ need to have waits in your tests.
Simon
One way of dealing with this problem is to add a unique key to the
"window" global before performing the action that loads the page. A
page reload will cause this variable to be deleted, so it's an easy
thing to check for.
Regards,
Simon