Re: [Wtr-general] Problem with running tests in a suite

2005-08-30 Thread Bret Pettichord
For IE Controller: http://rubyforge.org/frs/shownotes.php?release_id=241 * Added fix for the RPC intermittent bug that would occur of an instance of ie/iec was created too soon after a previous one was killed. Code change to def initialize(): # creating a new IE instance immediately

Re: [Wtr-general] Problem with running tests in a suite

2005-08-25 Thread Andy Sipe
I have exactly the same problem. The problem is made worse when running on slower computers.The testsuite 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 watirfail with this problem. I haven't come up

[Wtr-general] Problem with running tests in a suite

2005-08-24 Thread Lisa Crispin
If we have really small scripts/test cases, they run fine in a suite. But as we add code to them, we start having a problem where the first IE browser window does not shut down, and the second script errors out because there was a window already open. As the scripts get larger, this happens more

Re: [Wtr-general] Problem with running tests in a suite

2005-08-24 Thread Jeff Wood
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... On 8/24/05, Lisa Crispin [EMAIL PROTECTED] wrote: If we have really small scripts/test cases, they run

Re: [Wtr-general] Problem with running tests in a suite

2005-08-24 Thread Owen Rogers
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