Wednesday, September 27th, 2006

Selenium 0.8 Release

Category: Testing

Version 0.8 of the web application functional testing tool Selenium has been released.

Jeff Xiong explaing the new features:

  • A "multiWindow" option which places the application-under-test in a  separate window, allowing testing of "frame-busting" apps. In the past Selenium didn’t deal with the applications-under-test (AUT) which use frames very well, because it put the AUT in an embeded frame instead of stand-alone window. That was one of the largest problems preventing people from using Selenium. In 0.8, we provided an option to put the AUT in a stand-alone window, so that we can deal with all kinds of AUT actions that previously might have broken Selenium (e.g. change location of "window.parent" or ""). This is the most important improvement in this new version.
  •  More reliable page-load detection for popup windows. There’s a bug makes firefox cannot detect "children" windows’ page-load status. That means with the combination of older version of Selenium and firefox, there may be some unpredicatable test failures. In this new version we provided a firefox plugin, which enhances firefox and makes the test more reliable.
  • New cookie-management actions. The past versions cannot deal with cookies. Users had to set up cookie environment in AUT by themselves to test cookie-related functionalities like "login". 0.8 provided cookie-handling actions like "createCookie", "deleteCookie" and "storeCookie", so that users can setup and teardown cookie environment in test cases.
  • Run-speed slider and "Pause" button which replace the old Run/Walk/Step radio-buttons.  In past versions we provided only 2 different speed
    options: fast "Run" and slow "Walk". In 0.8 we provided a slider to control the speed. Users can choose any speed between "very fast" and "very slow", allowing them to observe the tests in action.

Jeff has a nice article on Testing Ajax applications with Selenium over at InfoQ.

Posted by Dion Almaer at 9:31 am

3.8 rating from 25 votes


Comments feed TrackBack URI

Sadly they still haven’t added support for inter-domain scripting using the document.domain property. Due to browser security model oddness, you can’t reliably change the document.domain property after certain document or window properties are read. Without in-built support for changing the domain on startup it’s difficult to test apps that need to change the domain. Ahh well, the new features still sound good, and should improve the stability.

Comment by Patrick Myles — September 27, 2006

The frames and popup problems were a huge blocking issue at our company for using Selenium and I’m really glad they say they fixed it. Can’t wait to try it out again.

Comment by jc — September 28, 2006

The frame and popup issue is still there and I do not expect it to be solved in the near future. selenium’s browserbot only listens to the top level window for open events; open events from nested windows like frames inside framesets aren’t detected. The workaround I am using is: open popups via top window as long as we are running under selenium.

Comment by mrtin — October 16, 2006


teen movie sumzyuxfdc

Trackback by teen movie — November 13, 2006

The synchronization problem is not so simple. The
evalid system provides various automatic internal sync modes
but that is seldom enough. So it ALSO includes things
like synchronization on matching a string (in any frame),
and synchronization on a DOM object (anywhere on the page).

eValid is a very advanced testing system, with a 100% guarantee
of testing playback success on every kind of website, including
and especially AJAX sites. Go to for a free eval
copies of eValid.


Comment by edward miller — December 11, 2006

Leave a comment

You must be logged in to post a comment.