Can you try if changing "\\" in that #click_no_wait command to "/" instead will make any difference. I can see this entry in that command: C:\\Users\\pauld\\workspace\\SopranoMedicalRecords\\AutomatedTests\\med_rec\\
Let us know of your results. Jarmo Pertman ----- IT does really matter - http://itreallymatters.net On Tuesday, October 9, 2012 6:29:16 AM UTC+3, Paul wrote: > > Edited subject to click_no_wait no worky on Ruby 1.9.3 > > On Monday, 8 October 2012 10:57:02 UTC+13, Paul wrote: >> >> Here is my ruby version and gem list (after re-installing Ruby 1.9.3 and >> gems): >> >> C:\Users\pauld\workspace\SopranoMedicalRecords\AutomatedTests\med_rec\tests>ruby >> >> -v >> ruby 1.9.3p194 (2012-04-20) [i386-mingw32] >> >> C:\Users\pauld\workspace\SopranoMedicalRecords\AutomatedTests\med_rec\tests>gem >> >> list >> >> *** LOCAL GEMS *** >> >> addressable (2.3.2) >> bigdecimal (1.1.0) >> builder (3.1.3) >> childprocess (0.3.5) >> commonwatir (4.0.0) >> ffi (1.1.5 x86-mingw32) >> hoe (3.1.0) >> io-console (0.3) >> json (1.5.4) >> libwebsocket (0.1.5) >> mini_magick (3.2.1) >> minitest (2.5.1) >> multi_json (1.3.6) >> nokogiri (1.5.5 x86-mingw32) >> rake (0.9.2.2) >> rautomation (0.7.2) >> rdoc (3.9.4) >> ruby-oci8 (2.1.2 x86-mingw32) >> rubyzip (0.9.9) >> s4t-utils (1.0.4) >> selenium-webdriver (2.25.0) >> subexec (0.0.4) >> sys-proctable (0.9.1 universal-mingw32) >> user-choices (1.1.6.1) >> watir (4.0.0 x86-mingw32) >> watir-classic (3.2.0) >> watir-webdriver (0.6.1) >> win32-api (1.4.8 x86-mingw32) >> win32-process (0.7.0) >> win32screenshot (1.0.7) >> windows-api (0.4.2) >> windows-pr (1.2.2) >> xml-simple (1.1.1) >> yajl-ruby (1.1.0 x86-mingw32) >> >> Here is an IRB session, the button to click is deep within some frames. >> >> irb(main):014:0> require 'rubygems' >> => true >> irb(main):015:0> require 'watir-classic' >> => true >> irb(main):016:0> b = Watir::Browser.attach :url, /concerto/ >> => #<Watir::IE:0x..f953476 url=" >> http://chch-medsrec-vm04/concerto/Concerto.htm"; title="Concerto - >> Example Clinician"> >> irb(main):017:0> cc = b.frame(:id, 'ConcertoContext') >> => #<Watir::Frame:0x7a30ef0e located=false >> specifiers={:tag_name=>["frame", "iframe"], :id=>"ConcertoContext"}> >> irb(main):018:0> ca = cc.frame(:id, 'ConcertoApplication') >> => #<Watir::Frame:0x750f406 located=false >> specifiers={:tag_name=>["frame", "iframe"], :id=>"ConcertoApplication"}> >> irb(main):019:0> eds = ca.frame(:name, 'EDSMain') >> => #<Watir::Frame:0x..f91b2c866 located=false >> specifiers={:tag_name=>["frame", "iframe"], :name=>"EDSMain"}> >> irb(main):020:0> r = eds.frame(:name, 'Right') >> => #<Watir::Frame:0x..f8e09a25e located=false >> specifiers={:tag_name=>["frame", "iframe"], :name=>"Right"}> >> irb(main):021:0> l = eds.frame(:name, 'Left') >> => #<Watir::Frame:0x3d17c2c6 located=false >> specifiers={:tag_name=>["frame", "iframe"], :name=>"Left"}> >> irb(main):022:0> lt = l.frame(:name, 'LeftTop') >> => #<Watir::Frame:0x..f860f0e9e located=false >> specifiers={:tag_name=>["frame", "iframe"], :name=>"LeftTop"}> >> irb(main):023:0> lb = l.frame(:name, 'LeftBottom') >> => #<Watir::Frame:0x19ca55c6 located=false >> specifiers={:tag_name=>["frame", "iframe"], :name=>"LeftBottom"}> >> irb(main):024:0> lb.button(:id, 'exitButton').exist? >> => true >> irb(main):025:0> lb.button(:id, 'exitButton').click_no_wait >> => "" >> irb(main):026:0> lb.button(:id, 'exitButton').click >> *[Manually clicked Ok button on javascript dialog]* >> => 0.065006 >> irb(main):027:0> >> >> >> When I run from my framework you can see a flash (looks like a cmd window >> for a split second) as if the button is clicked (click_no_wait) but the >> javascript dialog box does not appear as it did with watir versions prior >> to 1.7.1. >> Running from IRB as above I do not see that flash. >> If I do a button.click the dialog box appears and blocks the script. >> >> Looking at the Ruby source there is not a click_no_wait method in >> element.rb but the method is being called otherwise I would get a no method >> exception. >> >> Am I missing something here? >> >> thanks >> - paul >> >> >> On Friday, 5 October 2012 22:18:46 UTC+13, Jarmo Pertman wrote: >>> >>> I can't see Watir 4.0 in your gemlist. Can you show us minimal example >>> of your code, which fails (e.g. require statements, browser initialization)? >>> >>> Jarmo Pertman >>> ----- >>> IT does really matter - http://itreallymatters.net >>> >>> >>> On Friday, October 5, 2012 12:13:22 AM UTC+3, Paul wrote: >>>> >>>> Here is my gem list: >>>> >>>> C:\Ruby193\lib\ruby\gems\1.9.1\gems>gem list >>>> >>>> *** LOCAL GEMS *** >>>> >>>> addressable (2.3.2) >>>> bigdecimal (1.1.0) >>>> builder (3.1.3) >>>> childprocess (0.3.5) >>>> commonwatir (4.0.0, 3.0.0) >>>> ffi (1.1.5 x86-mingw32) >>>> hoe (3.1.0) >>>> io-console (0.3) >>>> json (1.5.4) >>>> libwebsocket (0.1.5) >>>> mini_magick (3.2.1) >>>> minitest (2.5.1) >>>> multi_json (1.3.6) >>>> nokogiri (1.5.5 x86-mingw32) >>>> rake (0.9.2.2) >>>> rautomation (0.7.2) >>>> rdoc (3.9.4) >>>> ruby-oci8 (2.1.2 x86-mingw32) >>>> rubyzip (0.9.9) >>>> s4t-utils (1.0.4) >>>> selenium-webdriver (2.25.0) >>>> subexec (0.0.4) >>>> sys-proctable (0.9.1 universal-mingw32) >>>> test-unit (2.5.2) >>>> user-choices (1.1.6.1) >>>> watir-classic (3.2.0) >>>> watir-webdriver (0.6.1) >>>> win32-api (1.4.8 x86-mingw32) >>>> win32-process (0.7.0) >>>> win32screenshot (1.0.7) >>>> windows-api (0.4.2) >>>> windows-pr (1.2.2) >>>> xml-simple (1.1.1) >>>> yajl-ruby (1.1.0 x86-mingw32) >>>> >>>> On Friday, 5 October 2012 09:52:31 UTC+13, Paul wrote: >>>>> >>>>> Hi, I have just upgraded my framework to 1.9.3 and watir 4.0, I am >>>>> using watir-classic 3.2.0. I have been using click_no_wait but now it >>>>> does >>>>> not work and I can't find the method in the source. element.rb no longer >>>>> has this method! >>>>> >>>>> If I can't solve this I will try to patch it in or downgrade watir. >>>>> >>>>> - thanks >>>>> >>>> -- Before posting, please read http://watir.com/support. In short: search before you ask, be nice. [email protected] http://groups.google.com/group/watir-general [email protected]
