[wtr-general] Unable to open IE window

2009-02-05 Thread Jaz
Hi! Recently installed ruby to use watir, and I get a strange error when I execute the steps in "Watir in 5 minutes" http://wiki.openqa.org/display/WTR/Watir+in+5+Minutes These are the steps I follow: 1. require "watir" 2. ie = Watir::IE.new When I perform step 2 I get the following error:

[wtr-general] Re: Unable to open IE window

2009-02-05 Thread Jaz
How do I do that? On Feb 5, 12:36 pm, aidy lewis wrote: > At a guess try updating your windows api gem > > Aidy > > 2009/2/5 Jaz : > > > > > > > Hi! > > > Recently installed ruby to use watir, and I get a strange error when I > >

[wtr-general] Re: Unable to open IE window

2009-02-05 Thread Jaz
Hi! Thanks for answering so fast Aidy Unfortuneatly it still doesn't work =( (Going crazy soon...) /jasmin On Feb 5, 1:59 pm, aidy lewis wrote: > gem list -r win* > > gem update windows-api -y > > Aidy > > 2009/2/5 Jaz : > > > > > > > How do

[wtr-general] Re: Unable to open IE window

2009-02-05 Thread Jaz
ose gems. > > > Charley Baker > > blog:http://charleybakersblog.blogspot.com/ > > Lead Developer, Watir,http://wtr.rubyforge.org > > QA Architect, Gap Inc Direct > > > On Thu, Feb 5, 2009 at 6:51 AM, aidy lewis > > wrote: > > >> This w

[wtr-general] Re: Unable to open IE window

2009-02-06 Thread Jaz
t; require "watir" > > ie = Watir::Browser.new > > ie.goto "http://www.google.com"; > > ie.text_field(:name, "q").set "WSO2 WSAS" > > ie.button(:name, "btnG").click > > Call me on Google Talk if you have problems. > >

[wtr-general] Re: Unable to open IE window

2009-02-09 Thread Jaz
nv > > to know what version of rubygems and ruby you run > > > > On Fri, Feb 6, 2009 at 7:24 AM, Al Snow wrote: > > > Jasmin, > >      Run "gem list" and send the output to this mailing list so we > > can see your installed gems. > > Thanks, >

[wtr-general] Re: Unable to open IE window

2009-02-13 Thread Jaz
erefore, would be uninstall these gems and then > >>> reinstall them. > > >>> Bret > > >>> Charley Baker wrote: > > >>>> It seems there are some compatibility issues here with some of the > >>>> win32utils. Try updating your wi