> Bret Pettichord wrote:
>
> > This code works with 1.5.
>
> Can I install that from gem?
I just found watir-1.5.1.1065.gem, and the E went away in the test run.
Now how to get rid of all the IEs that pop up in a tested state during the run?
--
Phlip
http://c2.com/cgi/wiki?ZeekLand <-- NOT
Of all the solutions in the FAQ, the only one that works for me is
@ie.logger.level = Logger::ERROR
and that solution works great with Watir-1.4.1. I'd really like to use new
features in 1.5.1 -- especially the ability to create a new process for each
IE. I tried the same code with Watir 1.5.1
Bret Pettichord wrote:
> We've often had reports of problems when suites repeatedly open and
> close IE windows. I mostly avoid it, and wrote the code i sent you
> because i had a case where i couldn't, and i wanted to manage IE at the
> process level, rather the OLE way that Watir has traditional
Bret Pettichord wrote:
> This code works with 1.5.
Can I install that from gem? It seems to give 1.4.1 reliably.
Right now, please assume I know nothing, to avoid I have to re-ask
stuff. When I used CVS to get the HEAD of WTR (I know _almost_
nothing;), it gives a cliec folder containing an inst
This code works with 1.5.
Phlip wrote:
> Bret Pettichord wrote:
>
>
>> Use this instead.
>> def IE.new_process
>>iep = IEProcess.start
>>ie = IE.bind iep.window
>>
>
> That givin':
>
> 1) Error:
> test_fetchTestResult(TestCGIWithWatir):
> NoMethodError: undefined method `bind' f
Phlip wrote:
> Bret Pettichord wrote:
>
>
>> (I plan to commit this to Watir, but since you asked, i'm sending it
>> direct. Using this you do ie = IE.new_process to create an IE and
>> ie.kill to close it. This creates a separate IE process for each Window
>>
>
> If my current system turns
Bret Pettichord wrote:
> Use this instead.
> def IE.new_process
>iep = IEProcess.start
>ie = IE.bind iep.window
That givin':
1) Error:
test_fetchTestResult(TestCGIWithWatir):
NoMethodError: undefined method `bind' for Watir::IE:Class
./tests/ieProcess.rb:78:in `new_process'
./
Bret Pettichord wrote:
> (I plan to commit this to Watir, but since you asked, i'm sending it
> direct. Using this you do ie = IE.new_process to create an IE and
> ie.kill to close it. This creates a separate IE process for each Window
If my current system turns ruby.exe off at the end of a test
Phlip wrote:
> Watirists:
>
> After running a test with Watir over and over again, my WinXP box
> shows signs of "handle exhaustion". Simple windows and such don't
> open. This shows that when Watir creates its secret Internet Explorer
> object, and destroys it (wie.close(), right?) something leaks
