Dan Fabulich wrote:
So, to put your point another way, JsUnit *can* handle transitions between pages: you just have to code an entire BrowserBot on top of JsUnit to make it do that. (Which, thankfully, you already have.)
Remember when I wrote this a couple of weeks ago? Well, uhm, I'm wrong and I'm sorry. :-)
What I didn't realize was that on most browsers the JavaScript interpreter is single-threaded; background threads can add items to the queue of work to be done, but as long as any function is sleeping, (busy-wait, applet sleep, synchronous XmlHttpRequest, whatever,) no other *JavaScript* work will happen in the background.
Would it change your mind if I translated the entire Selenium test suite into JsUnit tests? ;-)
... and therefore it is totally impossible for me to do this translation as I had so brazenly suggested. Instead, you're right, everyone should just code JsUnit-style tests in the Selenium framework (perhaps using my "eval" extension as an aid).
-Dan _______________________________________________ Selenium-users mailing list Selenium-users@lists.public.thoughtworks.org http://lists.public.thoughtworks.org/mailman/listinfo/selenium-users
