Official Selenium Blog

June 1, 2011

Selenium 2.0rc1: The Grid Release

Filed under: Releases — shs96c @ 5:35 pm UTC

We’re very happy to announce the first Release Candidate for Selenium 2, available for Java, C#, Ruby and Python. The API has been stabilised and the functionality needed for the final 2.0 release is mostly in. We’re going to be working hard to get there as soon as possible, but now’s the perfect time to test the waters and provide us with any feedback you may have! Grab the downloads from the site!

Highlights:

  • Grid 2: A major feature of this release is Grid 2, an implementation of the Selenium Grid that supports WebDriver’s wire protocol, allowing tests using Selenium WebDriver to be distributed through it. There are some docs to help you get started on the wiki.
  • New ChromeDriver: Following a complete rewrite of the ChromeDriver, Selenium 2 is now supported natively by the Chrome browser itself. In order to use this, you must download the chromedriver executable from the Selenium project site.
  • OperaDriver support: We’ve bundled the most excellent OperaDriver into the release to make it easy to get started testing with Opera.
  • Support for native events in Firefox 4.
  • Advanced User Interactions: An API that allows you to model complex user interactions, such as clicking on an element, holding the shift key, clicking on three more, and then dragging the four elements to a final destination. The entry point to this API is the Actions class.

We’ve also deleted all methods that were deprecated in 2.0b3 and have marked a number of methods and classes (notably RenderedWebElement and WebElement.getValue) deprecated. These will be deleted in the next release.

Known issues:

  • Native events on Linux may not work properly on tests that include alerts and prompts.
  • Mouse actions using the Advanced User Interactions API may not work properly for elements that have to be scrolled into view.

We plan on making our releases more frequent in the run up to 2.0final and polish off the bugs and issues. Stay tuned! This is going to be fun🙂

15 Comments »

  1. I remember reading Simon posing something about having RemoteWebElement and WebElement being undesirable. Since it’s now being deprecated, does that mean that isVisible is being moved over to the WebElement interface instead? It would be a shame to lose that functionality.

    Comment by theotherian — June 1, 2011 @ 7:17 pm UTC | Reply

    • We’ve moved almost all the methods up to WebElement itself, or out into the new user interactions API. The functionality of “isVisible” is still there🙂

      Comment by shs96c — June 1, 2011 @ 9:21 pm UTC | Reply

  2. Grid 2 seems to be the most awaited component now since most of us moved to selenium 2 long back , Great work Selenium Commiters

    Comment by Ajay K — June 1, 2011 @ 10:23 pm UTC | Reply

  3. You guys basically nailed every frustration I’ve had with Selenium 2 over the past few weeks. Stellar work.

    Comment by Tyson — June 2, 2011 @ 4:02 am UTC | Reply

  4. Great!

    Anyone knows when the jars are going to available on Maven?

    Cheers!

    Comment by martino — June 2, 2011 @ 8:01 am UTC | Reply

  5. Great news! Fantastic work !
    If someone wants to use power of Selenium2 Webdriver from PHP (phpunit) I can recommend my project: http://code.google.com/p/php-webdriver-bindings/ .
    It uses Json Wire Protocol to communicate with Selenium server.

    Comment by kolec — June 2, 2011 @ 9:36 am UTC | Reply

  6. […] Selenium 2.0rc1 has been released. […]

    Pingback by Selenium 2.0rc1 Released | TurboLinux Blog — June 2, 2011 @ 1:14 pm UTC | Reply

  7. Hi again,

    sorry for the spam, I im trying this rc1, Firefox is working well but IE8 is not starting… anyone else is having the same issue?

    Cheers

    Comment by martino — June 2, 2011 @ 2:41 pm UTC | Reply

    • Others were. We’ve just pushed RC2 to fix it.

      Comment by shs96c — June 2, 2011 @ 5:08 pm UTC | Reply

  8. […] Check out the official post here […]

    Pingback by Selenium 2 – Grid release | Open source SW tools — June 7, 2011 @ 9:23 am UTC | Reply

  9. rc2 is not working for me in safari 4.0.5 (531.22.7)
    It’s not populating the browser with the url of the test plan. Instead it’s putting in a local pathname
    file:///c:/DOCUME~1/username/LOCALS~1/Temp/customProfileDir0e03f54b6c8e48108bfde90b39490441/core/Blank.html?start=true

    With log turned on it just keeps saying
    debug(NNNNNNNN): currentTest.continueTestAtCurrentCommand()
    debug(NNNNNNNN): currentTest.continueTest() – acquire the next command
    error(NNNNNNNN): xmlHttp returned: 0:

    Does anyone else have such problems?

    Works for all my other browsers.

    Comment by bcowgillft — June 10, 2011 @ 2:29 pm UTC | Reply

  10. Why was WebElement.getValue deprecated? What’s is the replacement for it?

    Comment by Selenium — June 14, 2011 @ 11:18 pm UTC | Reply

    • It’s in the docs, but use WebElement.getAttribute(“value”) instead.

      Comment by shs96c — June 18, 2011 @ 7:50 pm UTC | Reply


RSS feed for comments on this post. TrackBack URI

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Blog at WordPress.com.

%d bloggers like this: