Official Selenium Blog

July 18, 2011

Selenium 2.1 Released

Filed under: Releases — shs96c @ 11:03 pm UTC

Now that Selenium 2 has been released, one of the goals of the project is to provide regular updates to our users and the community. The aim is for these updates to be small and manageable, incrementally addressing issues and problems raised by you. Selenium 2.1, which is launched today, marks the first of these regular, small releases.

Selenium 2.1 is largely focused on improving Grid with a host of minor improvements including better tracking of “orphaned” browser instances. There are also some bug fixes in the Firefox and IE WebDrivers, particularly when dealing with elements that are just off screen, and in making the Selenium RC emulation in the Java bindings more robust when confronted with pages that haven’t started loading.

As you can see, this is a “bite size” release, but we’d love to know: would you prefer these small, swift releases or larger ones? Please answer in the comments, or on the mailing list!

34 Comments »

  1. I prefer small releases!!

    Comment by dario — July 18, 2011 @ 11:33 pm UTC | Reply

  2. +1 for “bite size” releases, as long as each release is reflected in the Maven repo. We depend on the repo to update our instances of Selenium.

    Comment by Robert — July 18, 2011 @ 11:50 pm UTC | Reply

  3. +1 for the smaller bite size releases.

    Comment by Kelly Summerlin — July 19, 2011 @ 12:06 am UTC | Reply

  4. Glad to see 2.1 so soon. Small, swift releases are much preferred. Ideally with changelogs, so I can tell whether the hassle of upgrading is worth it or not.

    Comment by Stephen — July 19, 2011 @ 4:03 am UTC | Reply

  5. Can we add social share button on this site? It would make it easy for us to share the post with others.

    ~tarun

    Comment by Tarun Kumar — July 19, 2011 @ 4:56 am UTC | Reply

    • That’s a great idea.

      Comment by shs96c — July 19, 2011 @ 7:40 am UTC | Reply

  6. We welcome small releases………

    Comment by Suresh — July 19, 2011 @ 5:30 am UTC | Reply

  7. small is beautiful…

    Comment by Barry Horgan — July 19, 2011 @ 5:46 am UTC | Reply

  8. this error is not so beautiful…

    Type is not resolved for member ‘OpenQA.Selenium.WebDriverException,WebDriver, Version=2.1.0.0, Culture=neutral, PublicKeyToken=null’..

    Comment by Barry Horgan — July 19, 2011 @ 6:22 am UTC | Reply

  9. Fast smaller versions is better than long waiting for large versions

    Comment by Manar Husrieh — July 19, 2011 @ 7:01 am UTC | Reply

  10. “release early, release often”

    Comment by Gian Marco Gherardi — July 19, 2011 @ 7:25 am UTC | Reply

  11. +1 for the smaller releases

    Comment by Pavol Pitoňák — July 19, 2011 @ 10:44 am UTC | Reply

  12. Smaller release would be better

    Comment by Raj — July 19, 2011 @ 11:09 am UTC | Reply

  13. Releases available in the maven repository even better

    Comment by Dr No — July 19, 2011 @ 11:39 am UTC | Reply

  14. Small updates, released frequently, with thorough change logs would be desirable.

    Comment by totallymeat — July 19, 2011 @ 1:44 pm UTC | Reply

  15. I agree that small releases not only address potential issues faster, but it also makes it easier to pin-point what has changed if a new version alters the result of existing tests.

    Comment by Visual C# Kicks — July 19, 2011 @ 2:33 pm UTC | Reply

  16. I thought this question was definitively answered in the 90’s: http://www.catb.org/~esr/writings/homesteading/cathedral-bazaar/ar01s04.html🙂
    Thank you for a great piece of software, and thank you for making my job easier!

    Comment by siking — July 19, 2011 @ 4:06 pm UTC | Reply

  17. Small and continuously like Mr. Fowler says😉

    Comment by Jackson Santos — July 19, 2011 @ 6:11 pm UTC | Reply

  18. +1 for quicker/smaller releases. To me this means bugs and issues can be addressed more quickly.

    +999999 for getting Maven artifacts release in lock-step with the other binaries. (sorry to beat the proverbial dead horse😉

    Comment by Jeff v. — July 19, 2011 @ 8:59 pm UTC | Reply

  19. Does this can be used with perl?

    Comment by dilip — July 20, 2011 @ 4:52 am UTC | Reply

  20. Hi All,

    I would prefere a “medium” releases, like 1 a month as we are using maven and every time we have to update the pom file!

    Cheers.

    Comment by martino — July 20, 2011 @ 7:27 am UTC | Reply

  21. +1 for medium releases (about once a month).

    What’s new in 2.1.0 ?
    You definitively need a Changelog page!!

    Comment by noirbizarre — July 20, 2011 @ 1:11 pm UTC | Reply

    • We’ll add a changelog to the source with 2.2, but this blog entry really does contain the major changes.

      Comment by shs96c — July 21, 2011 @ 10:35 am UTC | Reply

  22. My main concern is quality. Quick is fine as long as the QA process is rigorous. We use the application for QA ourselves, any quality issues in selenium would muck up that process.

    Comment by Chris Kretler — July 20, 2011 @ 9:31 pm UTC | Reply

  23. small, regular updates are good to keep the community of users active and encourage more usage which inturn boosts the developer community’s satisfaction. just a thought

    Comment by Ravitej A — July 21, 2011 @ 10:21 am UTC | Reply

  24. +1 for Quick is fine as long as the QA process is rigorous.

    Comment by Ivo Grootjes — July 21, 2011 @ 11:40 am UTC | Reply

  25. Small releases is a great idea. Also can we add a wordpress share to the blog?

    Comment by rivlin — July 21, 2011 @ 12:31 pm UTC | Reply

  26. I definitely prefer these short release which makes the bug fixes into users very quickly. Dont want to wait for too long🙂

    Comment by Densil D'silva — July 22, 2011 @ 3:15 pm UTC | Reply

  27. Count me in for small and swift! Great job!

    Comment by Bernard — July 22, 2011 @ 9:04 pm UTC | Reply

  28. I tried to upgrade to Selenium 2.1 yesterday and it was an incredibly confusing and frustrating process. Just changing the Maven dependencies did not do it – received many NoClassDefFound errors until I stumbled across someone’s entry in a forum about having to include the jars in the libs folder. After that, I ran into other issues with my tests built on the previous version of WebDriver. It would be EXTREMELY helpful if there was one location to go to for detailed documentation. I found there seemed to be many new classes and functions in the upgrade (Capabilities, for example – big for IE 8 users). I googled til my fingers bled and could not find adequate documentation explaining the new features and how to use them.

    A+ on the product, F– on the documentation. If someone knows of a good resource online, I’ll happily retract my comments.

    Thanks.

    Comment by Ed — July 26, 2011 @ 12:46 pm UTC | Reply

    • The information for maven users to get the latest version of selenium is linked to from project’s download page: http://seleniumhq.org/download/maven.html

      Comment by shs96c — July 26, 2011 @ 2:19 pm UTC | Reply

      • I only want to use the WebDrivers. I can update the versions of the WebDrivers just fine, it’s all the other dependencies for the jar files in libs folder that was the issue. Like I said, I got past all that and was able to build properly. However, once I try to run tests, I run into other issues (like the IE Capabilities problem) that I didn’t know about because I can’t find any detailed documentation on the new features.

        Comment by Ed — July 26, 2011 @ 2:30 pm UTC

  29. Filling out the form seems to work, but now I get this error when I click “Save”:

    org.openqa.selenium.WebDriverException: session c031afa0-480c-4c12-895f-135ea1809f2d does not exist
    Build info: version: ‘2.2.0’, revision: ‘13073’, time: ‘2011-07-26 00:54:48’
    System info: os.name: ‘Windows 7’, os.arch: ‘amd64’, os.version: ‘6.1’, java.version: ‘1.6.0_18’
    Driver info: driver.version: RemoteWebDriver

    Comment by Ed — July 26, 2011 @ 3:10 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: