mozilla/BrowserID-Tests — pull request #8 by jrgm (2012-03-13 00:16:18+00:00)
Title: wait for the signin and logout buttons to be displayed before clicking

On occasion, when running these tests in a continuous loop, the test fails most commonly because the signin button is not yet displayed/clickable but also because the element was not accessible in the dom yet. Can also happen, but much less commonly, in the logout case.

This is rare when running against production, but happens often enough when running against stage, perhaps because the heroku instances that beta.myfavoritebeer runs on may be lower end (or higher latency) than the instances that run myfavoritebeer.org.

Note 1: On a couple of occasions I have hit this error "Element is not clickable at point (650, 56). Other element would receive the click:" Is that possibly because the link postion moves at the last moment on a reflow in the page?

Note 2: self.timeout == 60000 in all the calls to WebDriverWait; do we need to adjust that by /1000 for webdriver calls?