This is a guest post from Douglas Squirrel, CTO at youDevise
Our Cruise Missile monitor records these failures for us so we can track them, and it lets us mark them so we know not to waste time on further investigation, but it’s still massively annoying when your build isn’t reliable!
- detect the dialog and, when you do, click it or else kill all browsers on the machine
- try proxy injection mode for IE under Selenium
- modify Selenium to fail the test and kill the browser when the dialog is detected
- wait for webdriver to merge with Selenium (it’s supposed to be more resilient in the face of evil dialogs)
- wait for IE to die
We’re trying to convince Julian to have a go at one of the first three (webdriver will surely ride to our rescue before the IE zombie falls over, but neither one seems likely before the next Star Trek movie). If we can get it working we’d like to make the solution open source, ideally part of Selenium. Surely others are suffering with the same problem and would benefit from an end to the Dialog of Doom. Stay tuned!
Image thanks to OiMax