I have exactly the same problem. The problem is made worse when running on slower computers. The test suite runs fine on higher speed development stations, but when run on a build box that is under considerable strain many of the tests written using watir fail with this problem. I haven't come up with any real good solution other than to sleep in teardown (which doesn't always work).
-andy
From: Owen Rogers <[EMAIL PROTECTED]>
Reply-To: [email protected]
To: [email protected]
Subject: Re: [Wtr-general] Problem with running tests in a suite
Date: Wed, 24 Aug 2005 20:00:35 -0400
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
_______________________________________________ Wtr-general mailing list [email protected] http://rubyforge.org/mailman/listinfo/wtr-general
