> > The way I write tests nowadays is to wait after every asynchronous action >> (be it loading a page where ajax calls are executed as part of the page >> load or interacting with an element which triggers ajax calls) for the page >> state to settle (asynchronous action to complete) before I move on to the >> next step in the test. >> > It's a separate issue, but I've a hard time with AngularJS assessing when the page is 'settled' and went the other path with implicit waiting. Thanks though, seems like a solid alternative.
-- You received this message because you are subscribed to the Google Groups "Geb User Mailing List" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/geb-user/e6850c61-167f-4c67-9f82-48125bb91c91%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
