Comments on: Selenium 0.8 Release

By: edward miller

edward miller — Tue, 12 Dec 2006 04:31:42 +0000

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 http://www.e-valid.com for a free eval
copies of eValid.

-EFM

By: teen movie

teen movie — Mon, 13 Nov 2006 13:16:53 +0000

teen

teen movie sumzyuxfdc

By: mrtin

mrtin — Mon, 16 Oct 2006 10:49:07 +0000

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.

By: jc

jc — Thu, 28 Sep 2006 09:36:17 +0000

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.

By: Patrick Myles

Patrick Myles — Wed, 27 Sep 2006 22:45:19 +0000

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.