Selenium is Groovy

UI-Element has been integrated into Selenium Core in the project’s subversion repository for some time now. This means no special tricks are necessary to use it – just specify your map file as a user extension! I’m posting this announcement mainly because it seems my original UI-Element post is at the top of Google’s search results, and I wanted to make clear that some things have changed significantly since it was published (but don’t want to rewrite the thing … you know, for posterity!).

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.

4 Responses to “Selenium is Groovy”

  1. Giuliano Says:

    I’m trying to use TestRunner with UI-Element. Is this possible? UI-Element works great with Selenium IDE; however, I received an error ” Unrecognized locator” when I try to run the same testcase with TestRunner. If they are compatible, how to do I include the files.

    Thanks.

  2. gyrm Says:

    Hi,

    You probably need to update the version of Selenium (Core?) you’re using. Try downloading a nightly snapshot from OpenQA.

  3. Kristjan Says:

    Hi,

    Sorry for posting here, but clearspace.openqa.org still seems to have technical problems…
    I’m part of a research group that’s researching Cross-Browser Compliant Rich Internet Application Design and Testing. In our search for a toolset to cover automating code validation, visual comparison and testing of functional behavior I came across snapsIE.
    I’d like thank you for making snapsIE. And ask if you ever thought about how hard it would be to implement similar solutions on other browsers (opera, safari, google chrome…) so it would work on both the Selenium RC and Core?

    Best regards,
    Kristjan

  4. gyrm Says:

    Hi Kristjan,

    The cool thing about taking screenshots using captureEntirePageScreenshot for Firefox and snapsIE for IE is that both commands work for Core. One of the main hurdles is saving the image to disk – you need to somehow obtain privilege escalation to do this. I imagine getting the image data would be possible for Safari and perhaps some of the other browsers via toDataUrl(); however, how are you going to save the image? This is probably more doable in the context of the RC-only.

    snapsIE is sort of limited … I’m glad you’re finding it useful. Unfortunately I got quite frustrated trying to get it to work for HTA mode, and have abandoned that unfruitful effort.

    Best,
    Haw-Bin

Leave a Reply


Bad Behavior has blocked 244 access attempts in the last 7 days.