On 24/08/05, Jeff Wood <[EMAIL PROTECTED]> wrote: > add a setup function to your test case to create a new instance for > each test then, add a teardown function and force the browser to go > away. ( ie.quit ) > > that should take care of things...
actually, this doesn't quite work. ie.quit/close is an asynchronous call to the ie com server. as a result, the new instance of ie that you create in your setup may connect to a com server that is in the process of shutting down. you can "fix" this with a sleep in your teardown, but it's pretty ugly and unreliable. this is a big problem for watir IHMO. i faced the same problem with a testing wrapper that i wrote for IE in C#. can't remember if i managed to fix it or not. cheers, owen. -- Owen Rogers | http://dotnetjunkies.com/weblog/exortech | CruiseControl.NET - http://ccnet.thoughtworks.com _______________________________________________ Wtr-general mailing list [email protected] http://rubyforge.org/mailman/listinfo/wtr-general
