I have a simple page that returns an ajax error / error message on presentation. The form is submitted using the standard ASP.Net link button.
My Selenium test correctly clicks the linkbutton button, however, the click time ends and crashes. The rest of the conditions of the test pass (since Selenium successfully clicks the link and a message about successful ajax is displayed).
All I can think of is that for some reason click () calls waitForPageToLoad, so it turns off. Is there any way to suppress this, or am I barking the wrong tree?
Is there an alternative way to handle a click that does not care about what happens after the event fires?
Additional Information: Selenium IDE 1.0.2 is hosted on Firefox 3.5.2 on Vista (don't ask)
Bypass
I managed to pass my test by creating my own click () function in user-extensions.js, which does not call Selenium.decorateFunctionWithTimeout (). While my test really passes, this is not an ideal solution.
If you want to try this yourself, add the following to user-extensions.js (make sure you link to this file in the Se: IDE configuration using Tools | Selenium IDE | Options | Options | General | Selenium Core extensions)
Selenium.prototype.doBeatnicClick = function(locator) {
var element = this.browserbot.findElement(locator);
var elementWithHref = getAncestorOrSelfWithJavascriptHref(element);
if (browserVersion.isChrome && elementWithHref != null) {
var win = elementWithHref.ownerDocument.defaultView;
var originalLocation = win.location.href;
var originalHref = elementWithHref.href;
elementWithHref.href = 'javascript:try { '
+ originalHref.replace(/^\s*javascript:/i, "")
+ ' } finally { window._executingJavascriptHref = undefined; }';
win._executingJavascriptHref = true;
this.browserbot.clickElement(element);
}
this.browserbot.clickElement(element);
};
Restart Se: IDE and you will have access to a new command, beatnicClick (), which should work where you experience click () timeout.
We hope that this will be fixed or fixed in the next version of Se: IDE.