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 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 consistently.
>
> We're working around this by putting in sleeps, but that seems like a
> hack and potentially unreliable. What am I missing here? One of my
> Java programmer coworkers who knows some Ruby looked at it with me,
> but couldn't come up with any other solution.
>
> Here is what my suite looks like. Maybe there's a better way to do the suite?
>
> $:.push("../lib")
> $:.push("../scripts/simple")
>
> require 'test/unit'
> require 'Payroll/tc_manage_groups'
> require 'Payroll/tc_create_payroll'
>
> thanks,
> Lisa
>
> _______________________________________________
> Wtr-general mailing list
> Wtr-general@rubyforge.org
> http://rubyforge.org/mailman/listinfo/wtr-general
>
--
"So long, and thanks for all the fish"
Jeff Wood
_______________________________________________
Wtr-general mailing list
Wtr-general@rubyforge.org
http://rubyforge.org/mailman/listinfo/wtr-general
