Selenium Blog

We’ve just released Selenium 2.0b2. If you’re the impatient sort who loves to have the latest and greatest, head over to the download site and get it while it’s hot. If you’re a Python user, then all you need to do is a simple “pip install -U selenium”. Ruby users can, as ever, simply run “gem install selenium-webdriver”. Maven users need to wait just a little bit longer: we’re going to be checking the release in ASAP.

Between beta 1 and beta 2, we held a week-long Bug Bash, during which we closed a significant number of bugs. From a user’s perspective, other highlights include:

• A more stable, capable iPhone driver.
• Updated Android driver.
• Improved python bindings for Selenium WebDriver. The namespace is now “selenium.webdriver”
• Added “Selenium.getCssCount” to mirror “Selenium.getXpathCount”
• “WebElement.getText()” performs more consistently across different browsers.
• Mono users can use the .Net bindings
• Continued to improve the WebDriverBackedSelenium. If you’re looking to migrate from Selenium 1 to Selenium 2, and want to take your time, this is a useful stepping stone.
• Reworked the Advanced User Interactions APIs. The big change is that the WebDriver APIs no longer rely on classes from the AWT.
• .Net users now have more support classes, to make writing tests less tiresome.
• The remote webdriver makes better use of sockets, which improves stability and scalability on Windows.
• Started to add support for driving multiple IE instances. This is considered experimental, but we’d love to hear it’s working for you!

If you’re interested in the guts of Selenium 2 and how it worked, then you might find these interesting:

• Continued reworking the IE and iPhone drivers to use the Automation Atoms.
• Reworked the structure of the source tree to be more language focused.
• We have the skeleton of a webdriver-backed selenium for Python.

As you can see, this is a big release. Beta 3 should be out a lot more quickly, and will be focusing on improving support for IE 9 and Firefox 4. Over the course of the 2.0b3 development, we shall also be removing as many deprecated methods as possible, so be sure to remove deprecation warnings from your builds when using 2.0b2!

Share this:

There isn’t an official announcement anywhere (yet) but Selenium 2.0b2 was released a couple hours ago. Time to upgrade all your servers. Beta 3 is going to focus on IE9 and FF4 support.

Meanwhile…

• A Webinar on Automated Selenium Testing with Maestro 3 could be interesting if you are considering the Maestro platform.
• And sticking with the webinar idea, Sauce Labs is hosting Selenium 2 Webinar: The Next Generation of Web and Mobile Application Testing
• After a bit of stagnation, the official Python drivers are starting to get updated again.
• After almost a year, a new version of js-test-driver is out.
• Selenium Sushi is a support library / package for .NET
• Window Driver Pattern for Acceptance Tests illustrates Page Objects for PHP (though I don’t think it goes as far as it should in terms of abstractions).
• Aside from locators, the next biggest pain point is synchronization. Advanced Selenium Synchronization with ‘Latches’ is how I address that.
• Need an easy way to communicate Selenese steps on something like Stack Overflow? The Separated Values Formatter could be just the trick.
• Selenesse is a mash-up of Fitnesse and Selenium. If you are going to StarEast and want to learn it from one of the maintainers then Want to learn SeleNesse hands-on? is for you.
• Your automated acceptance tests needn’t be written in the same language as your system being tested explains a trap that too many teams fall into

Share this:

I think the word that I’m looking for is “wow”. Perhaps “Wow!” would express the concept a little more clearly. Perhaps “WOW!” would be even clearer.  Yes, definitely. “WOW!” is a good way of describing this.

Before Christmas, Opera Software announced a pre-release of OperaWatir, an implementation of the Watir 2 API. What you may not know is that Watir 2 rests on the same WebDriver core as Selenium 2. Today, Opera made the source of the OperaDriver available on github: https://github.com/operasoftware/operadriver

This is “WOW!” It’s the first time a browser manufacturer has released their own implementation of the WebDriver APIs, and it shows how much Opera values test automation. Selenium 2 users now have an easy way to test that their sites work with Opera.

What are you waiting for? Go! Download! Test!

Share this: