At 07:00 PM 8/24/2005, Owen Rogers wrote:
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.
I remember complaining about this problem to Chris Morris when i was just a user of his IE Controller. I think he fixed it. Someone want to check the history of that project. Chris?
Maybe the answer is to avoid shutting down the COM server until you are done running tests.
One way would be to reuse the same client with your tests. That is what we do with the Watir unit tests. Another would be create an invisible ie at the beginning and not shut it down in the end. If we have one client reference, closing other ie instances won't also shutdown the server.
Bret _____________________ Bret Pettichord www.pettichord.com _______________________________________________ Wtr-general mailing list [email protected] http://rubyforge.org/mailman/listinfo/wtr-general
