Comments on: Selenium RC Per-Session Extension Javascript

By: Sybren

Sybren — Mon, 23 Aug 2010 08:40:12 +0000

I worked out a solution, check out my blog at http://stuvel.eu/archive/131/extending-selenium-from-the-client-driver for more information.

By: Sybren

Sybren — Thu, 19 Aug 2010 14:35:40 +0000

I’ve tried to extend the Selenium locators using the per-session extension script, and that also fails. I’ve posted a question about this on the selenium-users mailing list at http://groups.google.com/group/selenium-users/browse_thread/thread/4469b18f8909f2d

I’ll post back here when I get an answer on the list.

By: Ross Patterson

Ross Patterson — Fri, 19 Feb 2010 13:50:46 +0000

Just a heads-up for anyone trying to use this SetExtensionJS() interface. You can’t use this to create a Selenium command like you can with user-extensions.js, because the code that registers command handlers is run before SetExtensionJS() injects your code.

By: gyrm

gyrm — Fri, 09 Oct 2009 04:10:19 +0000

@ikostenko: I believe the strange behavior you’re seeing is due to your new Selenium command not following the semantics for the different “types” of commands, i.e. “actions” and “accessors”. Actions are named starting with “do”, while accessors are named starting with “get”. You can see in selenium-commandhandlers.js that the two are registered differently (look for _registerAllAccessors compared to _registerAllActions).

I think the return value of the command is used differently, depending on the type of command. Since you’re interested in actually returning a value (and not a condition closure or null), you probably want to use “getElement” instead of “doReturnElement”.

Hope it works out for you.

By: ikostenko

ikostenko — Tue, 22 Sep 2009 13:15:47 +0000

Sorry to post the following here, but I could not send you a message from clearspace.openqa.org due to their technical problems.

I have a problem with extending Selenium with a new command which returns something – it fails with ‘this.waitForCondition is not a function’ exception.

Below are my settings:

1. selenium-server.jar – user-extensions.js:

Selenium.prototype.doReturnElement = function(element) {
return this.browserbot.findElement(element);
};

2. selenium-java-client-driver.jar – Selenium.java
…
void returnText (String text);
…

DefaultSelenium.java
…
public void returnElement(String element) {
commandProcessor.doCommand(“returnElement”, new String[] {element});
}
…

3. MyTest.java:

…
public void testValidElement() {
selenium.returnElement(“//a”);
}

public void testInvalidElement() {
selenium.returnElement(“invalid”);
}
…

When running the test, different exceptions are thrown:

1. In case of non-existing element:
com.thoughtworks.selenium.SeleniumException: ERROR: Element invalid not found
at com.thoughtworks.selenium.HttpCommandProcessor.throwAssertionFailureExceptionOrError(HttpCommandProcessor.java:97)
at com.thoughtworks.selenium.HttpCommandProcessor.doCommand(HttpCommandProcessor.java:91)
at com.thoughtworks.selenium.DefaultSelenium.returnElement(DefaultSelenium.java:743)
at MyTest.testInvalidElement(MyTest.java)

2. In case of existing element:
com.thoughtworks.selenium.SeleniumException: this.waitForCondition is not a function
at com.thoughtworks.selenium.HttpCommandProcessor.throwAssertionFailureExceptionOrError(HttpCommandProcessor.java:97)
at com.thoughtworks.selenium.HttpCommandProcessor.doCommand(HttpCommandProcessor.java:91)
at com.thoughtworks.selenium.DefaultSelenium.returnElement(DefaultSelenium.java:743)
at MyTest.testValidElement(MyTest.java)

The latter exception is also thrown when the doReturnElement simply returns a string.

Thank you very much in advance,
Irina