Why not user browser.wait(fn, timeout) and set a really long timeout as the 2nd paremeter?
Em quarta-feira, 12 de março de 2014 09h26min35s UTC-3, Matt Calthrop escreveu: > > Hi > > I have a requirement to write several e2e tests that wait until the > contents of an element on the page change. > > The time this takes cannot be predetermined – but if it doesn't change > before the browser times out, then the test will be deemed to have failed. > > I could use *setInterval()* and *clearInterval()* to implement simple > polling functionality, but that doesn't quite seem the right way to go > about it. > > Anybody got any better suggestions? > > I'm using Protractor 0.20.1. > > cheers > > Matt > > -- You received this message because you are subscribed to the Google Groups "AngularJS" 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]. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
