Here’s the updated documentation link (if it doesn’t move again).

In other news, there is now a Groovy formatter for Selenium IDE, and support for a special GroovySeleneseTestCase which makes it possible to merge *AndWait commands into single commands. For example:

clickAndWait | foo

with the Java formatter translates into:

selenium.click("foo");
selenium.waitForPageToLoad("30000");

while the Groovy formatter simply says:

selenium.clickAndWait("foo")

Cleaner, and more expressive.

“Yeah, yeah! Eat that banana!” they holler at me.

I roll down the window. “Don’t you wish you had one too?” I call back.

There’s a stunned silence. I guess they didn’t expect me to reply, because for all the swagger in their voices a second ago, them seem to be a little sheepish now, not knowing what to say.

Emboldened, I continue: “Then all three of us could be sittin’ here, eatin’ bananas together!!!”

Now they’re really at a loss for words!

It should be now.

If you build from r2291 or greater from the RC trunk, you can play with it. Basically, the extension Javascript must be specified before the browser is launched, and stays in-play until the session is closed. A sample test has been checked in here:

SessionExtensionJsTest.java

This probably doesn’t work for proxy injection mode yet.

Happy extending!

Update

It appears too easy to encounter the “414 Request URI Too Large” issue. I’m looking into this.

Update

Looks like the 414 issue is related specifically to the Perl driver (see this Clearspace post); I noticed it when using Perl, but did not see the issue when running an equivalent test in Groovy:

import com.thoughtworks.selenium.*

class URILengthTest extends GroovyTestCase {
    def selenium

    @Override
    void setUp() {
        selenium = new DefaultSelenium('localhost',
            4444, '*firefox',
            'http://alistapart.com')
    }

    @Override
    void tearDown() {
        selenium.stop()
    }

    void testURILength() {
        def extensionJs = new File(
            'selenium-core/src/main/resources/core/scripts/ui-map-sample.js').text

        selenium.setExtensionJs(extensionJs)
        selenium.start()
        selenium.open('http://alistapart.com')
        selenium.click(
            'ui=allPages::section(section=topics)')
        selenium.waitForPageToLoad('5000')
    }
}

Update

Unfortunately, the 414 issue also affects the Python and Ruby client drivers (I just tested and verified this). I’m not about to fix them right this moment, so it appears the you can only truly take advantage of the per-session extension feature (i.e. include extensions of arbitrary size) in Java and Groovy for now. The good news is that this issue has already been reported, and JIRA tickets created (SRC-319 for Perl, SRC-321 for Python, SRC-322 for Ruby, and others for C# and PHP).

Thought I’d also expose the tool I mentioned earlier that I’ve been using to find the places to optimize. You can play with the jsprofile sample tests now without checking out any code. Cool!

Keep in mind that the sample Google News page contains very old news.