From watirjira at gmail.com Mon Aug 2 03:59:31 2010 From: watirjira at gmail.com (Zeljko (JIRA)) Date: Mon, 2 Aug 2010 02:59:31 -0500 (CDT) Subject: [Wtr-development] [JIRA] Commented: (WTR-450) Computer will be crashed when ie start In-Reply-To: <7741395.195.1280457871247.JavaMail.oqa-j2ee@openqa01.managed.contegix.com> Message-ID: <22617840.214.1280735971215.JavaMail.oqa-j2ee@openqa01.managed.contegix.com> [ http://jira.openqa.org/browse/WTR-450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=19736#action_19736 ] Zeljko commented on WTR-450: ---------------------------- What happens when you open IE manually? Is IE7 opened, or IE6? > Computer will be crashed when ie start > -------------------------------------- > > Key: WTR-450 > URL: http://jira.openqa.org/browse/WTR-450 > Project: Watir > Issue Type: Bug > Components: Wait > Affects Versions: 1.6.5 > Environment: MS win xp professional service pack2 > Reporter: ethen.hu > Fix For: 1.6.5 > > > This is my process to show issue when run watir > 1, First Ie6 exist, run watir to create ie instance, ie6 window will be created > 2, But When I update IE6 to IE7, and run watir to create IE instance, In theory, IE7 will be created, Actually, The IE6 window has been created. Now I have update ie6 to ie7, IE6 is not exist; well, watir will > create ie6 window which doesn't work one by one, more than 50 > Now , I found a function named 'window' in ie-process.rb, the condition for return is > "process_id == @process_id", Maybe this is the reason for issue I think. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.openqa.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From amit.esys at gmail.com Mon Aug 2 05:23:12 2010 From: amit.esys at gmail.com (Amit) Date: Mon, 2 Aug 2010 14:53:12 +0530 Subject: [Wtr-development] bring_to_front method doesn't work in FireWatir Message-ID: Hi All, i'm using firewatir for automating my application. When i use ff.bring_to_front method, it gives below error: *NoMethodError: undefined method `bring_to_front' for #* Any solution? Thank You -------------- next part -------------- An HTML attachment was scrubbed... URL: From zeljko.filipin at wa-research.ch Mon Aug 2 05:37:59 2010 From: zeljko.filipin at wa-research.ch (=?UTF-8?Q?=C5=BDeljko_Filipin?=) Date: Mon, 2 Aug 2010 11:37:59 +0200 Subject: [Wtr-development] bring_to_front method doesn't work in FireWatir In-Reply-To: References: Message-ID: On Mon, Aug 2, 2010 at 11:23 AM, Amit wrote: > NoMethodError: undefined method `bring_to_front' for # 3c0> Looks like bring_to_front is not implemented in firewatir. You can create a ticket: http://jira.openqa.org/browse/WTR This is the list for discussing watir development, in the future please see this page how to get support: http://watir.com/support/ ?eljko -- watir.com - community manager watirpodcast.com - host testingpodcast.com - audio podcasts on software testing. all of them vidipodkast.com - pri?amo o hardveru, softveru i ?asopisu Vidi -------------- next part -------------- An HTML attachment was scrubbed... URL: From notethan at gmail.com Mon Aug 2 12:18:35 2010 From: notethan at gmail.com (Ethan) Date: Mon, 2 Aug 2010 12:18:35 -0400 Subject: [Wtr-development] bring_to_front method doesn't work in FireWatir In-Reply-To: References: Message-ID: bring_to_front is implemented for Vapir-Firefox (see vapir.org ) On Mon, Aug 2, 2010 at 05:37, ?eljko Filipin wrote: > On Mon, Aug 2, 2010 at 11:23 AM, Amit wrote: > > NoMethodError: undefined method `bring_to_front' for > # > 3c0> > > Looks like bring_to_front is not implemented in firewatir. You can create a > ticket: > > > http://jira.openqa.org/browse/WTR > > This is the list for discussing watir development, in the future please see > this page how to get support: > > http://watir.com/support/ > > > ?eljko > -- > watir.com - community manager > watirpodcast.com - host > testingpodcast.com - audio podcasts on software testing. all of them > vidipodkast.com - pri?amo o hardveru, softveru i ?asopisu Vidi > > _______________________________________________ > Wtr-development mailing list > Wtr-development at rubyforge.org > http://rubyforge.org/mailman/listinfo/wtr-development > -------------- next part -------------- An HTML attachment was scrubbed... URL: From watirjira at gmail.com Mon Aug 2 21:31:31 2010 From: watirjira at gmail.com (huweihua (JIRA)) Date: Mon, 2 Aug 2010 20:31:31 -0500 (CDT) Subject: [Wtr-development] [JIRA] Commented: (WTR-450) Computer will be crashed when ie start In-Reply-To: <7741395.195.1280457871247.JavaMail.oqa-j2ee@openqa01.managed.contegix.com> Message-ID: <14829412.217.1280799091264.JavaMail.oqa-j2ee@openqa01.managed.contegix.com> [ http://jira.openqa.org/browse/WTR-450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=19737#action_19737 ] huweihua commented on WTR-450: ------------------------------ If I open IE manually,, IE7 opened. > Computer will be crashed when ie start > -------------------------------------- > > Key: WTR-450 > URL: http://jira.openqa.org/browse/WTR-450 > Project: Watir > Issue Type: Bug > Components: Wait > Affects Versions: 1.6.5 > Environment: MS win xp professional service pack2 > Reporter: ethen.hu > Fix For: 1.6.5 > > > This is my process to show issue when run watir > 1, First Ie6 exist, run watir to create ie instance, ie6 window will be created > 2, But When I update IE6 to IE7, and run watir to create IE instance, In theory, IE7 will be created, Actually, The IE6 window has been created. Now I have update ie6 to ie7, IE6 is not exist; well, watir will > create ie6 window which doesn't work one by one, more than 50 > Now , I found a function named 'window' in ie-process.rb, the condition for return is > "process_id == @process_id", Maybe this is the reason for issue I think. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.openqa.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From watirjira at gmail.com Sun Aug 8 17:23:31 2010 From: watirjira at gmail.com (Bret Pettichord (JIRA)) Date: Sun, 8 Aug 2010 16:23:31 -0500 (CDT) Subject: [Wtr-development] [JIRA] Commented: (WTR-450) Computer will be crashed when ie start In-Reply-To: <7741395.195.1280457871247.JavaMail.oqa-j2ee@openqa01.managed.contegix.com> Message-ID: <5869044.241.1281302611277.JavaMail.oqa-j2ee@openqa01.managed.contegix.com> [ http://jira.openqa.org/browse/WTR-450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=19740#action_19740 ] Bret Pettichord commented on WTR-450: ------------------------------------- Ethen, If you see code that you think should be changed, please change it and let us know if it fixes your problem. Huweihua, Are you the same person as Ethen Hu? > Computer will be crashed when ie start > -------------------------------------- > > Key: WTR-450 > URL: http://jira.openqa.org/browse/WTR-450 > Project: Watir > Issue Type: Bug > Components: Wait > Affects Versions: 1.6.5 > Environment: MS win xp professional service pack2 > Reporter: ethen.hu > Fix For: 1.6.5 > > > This is my process to show issue when run watir > 1, First Ie6 exist, run watir to create ie instance, ie6 window will be created > 2, But When I update IE6 to IE7, and run watir to create IE instance, In theory, IE7 will be created, Actually, The IE6 window has been created. Now I have update ie6 to ie7, IE6 is not exist; well, watir will > create ie6 window which doesn't work one by one, more than 50 > Now , I found a function named 'window' in ie-process.rb, the condition for return is > "process_id == @process_id", Maybe this is the reason for issue I think. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.openqa.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From watirjira at gmail.com Mon Aug 9 09:23:30 2010 From: watirjira at gmail.com (ethen.hu (JIRA)) Date: Mon, 9 Aug 2010 08:23:30 -0500 (CDT) Subject: [Wtr-development] [JIRA] Commented: (WTR-450) Computer will be crashed when ie start In-Reply-To: <7741395.195.1280457871247.JavaMail.oqa-j2ee@openqa01.managed.contegix.com> Message-ID: <5976035.251.1281360210742.JavaMail.oqa-j2ee@openqa01.managed.contegix.com> [ http://jira.openqa.org/browse/WTR-450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=19742#action_19742 ] ethen.hu commented on WTR-450: ------------------------------ To Bret Pettichord: Yes, It's me, > Computer will be crashed when ie start > -------------------------------------- > > Key: WTR-450 > URL: http://jira.openqa.org/browse/WTR-450 > Project: Watir > Issue Type: Bug > Components: Wait > Affects Versions: 1.6.5 > Environment: MS win xp professional service pack2 > Reporter: ethen.hu > Fix For: 1.6.5 > > > This is my process to show issue when run watir > 1, First Ie6 exist, run watir to create ie instance, ie6 window will be created > 2, But When I update IE6 to IE7, and run watir to create IE instance, In theory, IE7 will be created, Actually, The IE6 window has been created. Now I have update ie6 to ie7, IE6 is not exist; well, watir will > create ie6 window which doesn't work one by one, more than 50 > Now , I found a function named 'window' in ie-process.rb, the condition for return is > "process_id == @process_id", Maybe this is the reason for issue I think. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.openqa.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From watirjira at gmail.com Thu Aug 12 13:58:31 2010 From: watirjira at gmail.com (Jarmo Pertman (JIRA)) Date: Thu, 12 Aug 2010 12:58:31 -0500 (CDT) Subject: [Wtr-development] [JIRA] Updated: (WTR-449) making Element#click_no_wait faster and easier debuggable In-Reply-To: <16766026.183.1280354011131.JavaMail.oqa-j2ee@openqa01.managed.contegix.com> Message-ID: <27768487.319.1281635911245.JavaMail.oqa-j2ee@openqa01.managed.contegix.com> [ http://jira.openqa.org/browse/WTR-449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarmo Pertman updated WTR-449: ------------------------------ Description: I have been thinking of improving Element#click_no_wait for some time now. I can see the following problems with current solution: 1) code is not good - method _code_that_copies_readonly_array with funny comment in main namespace, eval_in_spawned_process with TODO and not-TODO comments 2) users have a lot of problems with click_no_wait (http://bit.ly/asirep) and current code doesn't allow easy debugging with monkey-patching or similar solutions 3) in the spawned process used for click_no_wait, no rubygems is loaded thus it's possible that users without having RUBYOPT set to -rubygems can't use click_no_wait and since it's hard to debug (see point #2) then they don't even know what's the problem 4) click_no_wait is just slow because it loads too many files/libraries in it's own process - it should just load all the necessary things and nothing else 5) currently, in the unit tests click_no_wait process doesn't use development libraries Here is a benchmark: *click_no_wait_bench.rb:* {noformat} require "rubygems" require "watir" require "benchmark" b = Watir::Browser.new b.goto "http://www.google.com" times = 5 # almost original watir 1.6.5 code # * added gsub to avoid bug for some ruby versions # * using ruby instead of start rubyw to measure time module Watir module PageContainer def eval_in_spawned_process(command) command.strip! load_path_code = _code_that_copies_readonly_array($LOAD_PATH, '$LOAD_PATH') ruby_code = "require 'watir/ie'; " # ruby_code = "$HIDE_IE = #{$HIDE_IE};" # This prevents attaching to a window from setting it visible. However modal dialogs cannot be attached to when not visible. ruby_code << "pc = #{attach_command}; " # pc = page container # IDEA: consider changing this to not use instance_eval (it makes the code hard to understand) ruby_code << "pc.instance_eval(#{command.inspect})" exec_string = "ruby -e #{(load_path_code + '; ' + ruby_code).inspect}".gsub("\\\"", "'") system(exec_string) end end end Benchmark.bmbm do |x| x.report("watir 1.6.5") {times.times {b.button(:name => "btnG").click_no_wait}} end =begin Rehearsal ----------------------------------------------- watir 1.6.5 0.031000 0.015000 0.046000 ( 26.136495) -------------------------------------- total: 0.046000sec user system total real watir 1.6.5 0.000000 0.000000 0.000000 ( 23.600350) =end # improved section # * simplified click_no_wait methods # * requiring rubygems incase of missing RUBYOPT # * extracted ruby_execute_command into method for easier monkey-patching for debugging and testing reasons module Watir class Element def click_no_wait assert_enabled highlight(:set) element = "#{self.class}.new(#{@page_container.attach_command}, :unique_number, #{self.unique_number})" @page_container.click_no_wait(element) highlight(:clear) end end module PageContainer def click_no_wait(element) ruby_code = "require 'rubygems';" << "require 'watir/ie';" << "#{element}.click!" system(spawned_click_no_wait_command(ruby_code)) end def spawned_click_no_wait_command(command) "start rubyw -e #{command.inspect}" end private :spawned_click_no_wait_command end end Benchmark.bmbm do |x| x.report("watir improved - ie") {times.times {b.button(:name => "btnG").click_no_wait}} end =begin Rehearsal ------------------------------------------------------- watir improved - ie 0.032000 0.047000 0.079000 ( 20.141152) ---------------------------------------------- total: 0.079000sec user system total real watir improved - ie 0.047000 0.016000 0.063000 ( 18.931083) =end # * loading watir/core.rb to reduce loading of unneeded files/libraries module Watir class Element def click_no_wait assert_enabled highlight(:set) element = "#{self.class}.new(#{@page_container.attach_command}, :unique_number, #{self.unique_number})" @page_container.click_no_wait(element) highlight(:clear) end end module PageContainer def click_no_wait(element) ruby_code = "require 'rubygems';" << "require '#{File.expand_path(File.dirname(__FILE__))}/watir/core';" << "#{element}.click!" system(spawned_click_no_wait_command(ruby_code)) end def spawned_click_no_wait_command(command) unless $DEBUG "start rubyw -e #{command.inspect}" else puts "#click_no_wait command:" command = "ruby -e #{command.inspect}" puts command command end end private :spawned_click_no_wait_command end end Benchmark.bmbm do |x| x.report("watir improved - click_no_wait") {times.times {b.button(:name => "btnG").click_no_wait}} end =begin Rehearsal ------------------------------------------------------------------ watir improved - click_no_wait 0.062000 0.015000 0.077000 ( 9.729557) --------------------------------------------------------- total: 0.077000sec user system total real watir improved - click_no_wait 0.015000 0.047000 0.062000 ( 9.308532) =end b.close {noformat} *watir/core.rb:* {noformat} require 'watir/win32ole' require 'logger' require 'watir/exceptions' require 'watir/matches' require 'watir/core_ext' require 'watir/logger' require 'watir/container' require 'watir/locator' require 'watir/page-container' require 'watir/ie-class' require 'watir/element' require 'watir/element_collections' require 'watir/form' require 'watir/non_control_elements' require 'watir/input_elements' require 'watir/table' require 'watir/image' require 'watir/link' require 'watir/html_element' require 'watir/waiter' require 'watir/module' {noformat} As it's possible to see from the results then i got click_no_wait to perform faster about 2-3 times (of course this depends on the PC and so on, but these are the results from my machine, which is a quite average laptop)! Results: 1) removed all this unnecessary and funny-looking code which also had slight of a "criminal overengineering" smell on it (http://coderoom.wordpress.com/2010/06/23/criminal-overengineering/) 2) it is now easy to debug #click_no_wait problems: {noformat} $DEBUG = true element.click_no_wait {noformat} 3) requiring rubygems always, just in case, in the spawned process 4) click_no_wait performs 2-3x faster! It might be possible to improve the performance even more by doing some larger changes with the require statements in watir/core.rb - unfortunately it is not possible anymore to make changes in smaller steps 5) all click_no_wait invocations in unit tests use now development libraries Fixes are in branch click_no_wait_patch: http://github.com/jarmo/watir/tree/click_no_wait_patch was: I have been thinking of improving Element#click_no_wait for some time now. I can see the following problems with current solution: 1) code is not good - method _code_that_copies_readonly_array with funny comment in main namespace, eval_in_spawned_process with TODO and not-TODO comments 2) users have a lot of problems with click_no_wait (http://bit.ly/asirep) and current code doesn't allow easy debugging with monkey-patching or similar solutions 3) in the spawned process used for click_no_wait, no rubygems is loaded thus it's possible that users without having RUBYOPT set to -rubygems can't use click_no_wait and since it's hard to debug (see point #2) then they don't even know what's the problem 4) click_no_wait is just slow because it loads too many files/libraries in it's own process - it should just load all the necessary things and nothing else 5) currently, in the unit tests click_no_wait process doesn't use development libraries Here is a benchmark: *click_no_wait_bench.rb:* {noformat} require "rubygems" require "watir" require "benchmark" b = Watir::Browser.new b.goto "http://www.google.com" times = 5 # almost original watir 1.6.5 code # * added gsub to avoid bug for some ruby versions # * using ruby instead of start rubyw to measure time module Watir module PageContainer def eval_in_spawned_process(command) command.strip! load_path_code = _code_that_copies_readonly_array($LOAD_PATH, '$LOAD_PATH') ruby_code = "require 'watir/ie'; " # ruby_code = "$HIDE_IE = #{$HIDE_IE};" # This prevents attaching to a window from setting it visible. However modal dialogs cannot be attached to when not visible. ruby_code << "pc = #{attach_command}; " # pc = page container # IDEA: consider changing this to not use instance_eval (it makes the code hard to understand) ruby_code << "pc.instance_eval(#{command.inspect})" exec_string = "ruby -e #{(load_path_code + '; ' + ruby_code).inspect}".gsub("\\\"", "'") system(exec_string) end end end Benchmark.bmbm do |x| x.report("watir 1.6.5") {times.times {b.button(:name => "btnG").click_no_wait}} end =begin Rehearsal ----------------------------------------------- watir 1.6.5 0.031000 0.015000 0.046000 ( 26.136495) -------------------------------------- total: 0.046000sec user system total real watir 1.6.5 0.000000 0.000000 0.000000 ( 23.600350) =end # improved section # * simplified click_no_wait methods # * requiring rubygems incase of missing RUBYOPT # * extracted ruby_execute_command into method for easier monkey-patching for debugging and testing reasons module Watir class Element def click_no_wait assert_enabled highlight(:set) element = "#{self.class}.new(#{@page_container.attach_command}, :unique_number, #{self.unique_number})" @page_container.click_no_wait(element) highlight(:clear) end end module PageContainer def click_no_wait(element) ruby_code = "require 'rubygems';" << "require 'watir/ie';" << "#{element}.click!" system(spawned_click_no_wait_command(ruby_code)) end def spawned_click_no_wait_command(command) "start rubyw -e #{command.inspect}" end private :spawned_click_no_wait_command end end Benchmark.bmbm do |x| x.report("watir improved - ie") {times.times {b.button(:name => "btnG").click_no_wait}} end =begin Rehearsal ------------------------------------------------------- watir improved - ie 0.032000 0.047000 0.079000 ( 20.141152) ---------------------------------------------- total: 0.079000sec user system total real watir improved - ie 0.047000 0.016000 0.063000 ( 18.931083) =end # * loading watir/core.rb to reduce loading of unneeded files/libraries module Watir class Element def click_no_wait assert_enabled highlight(:set) element = "#{self.class}.new(#{@page_container.attach_command}, :unique_number, #{self.unique_number})" @page_container.click_no_wait(element) highlight(:clear) end end module PageContainer def click_no_wait(element) ruby_code = "require 'rubygems';" << "require 'watir/core';" << "#{element}.click!" system(spawned_click_no_wait_command(ruby_code)) end def spawned_click_no_wait_command(command) "start rubyw -e #{command.inspect}" end private :spawned_click_no_wait_command end end Benchmark.bmbm do |x| x.report("watir improved - click_no_wait") {times.times {b.button(:name => "btnG").click_no_wait}} end =begin Rehearsal ------------------------------------------------------------------ watir improved - click_no_wait 0.062000 0.015000 0.077000 ( 9.729557) --------------------------------------------------------- total: 0.077000sec user system total real watir improved - click_no_wait 0.015000 0.047000 0.062000 ( 9.308532) =end b.close {noformat} *watir/core.rb:* {noformat} require 'watir/win32ole' require 'logger' require 'watir/exceptions' require 'watir/matches' require 'watir/core_ext' require 'watir/logger' require 'watir/container' require 'watir/locator' require 'watir/page-container' require 'watir/ie-class' require 'watir/element' require 'watir/element_collections' require 'watir/form' require 'watir/non_control_elements' require 'watir/input_elements' require 'watir/table' require 'watir/image' require 'watir/link' require 'watir/html_element' require 'watir/waiter' require 'watir/module' {noformat} As it's possible to see from the results then i got click_no_wait to perform faster about 2-3 times (of course this depends on the PC and so on, but these are the results from my machine, which is a quite modest laptop)! I call this as a quite big improvement if we think about all the Web 2.0 websites where #click_no_wait is often used. Results: 1) removed all this unnecessary and funny-looking code which also had slight of a "criminal overengineering" smell on it (http://coderoom.wordpress.com/2010/06/23/criminal-overengineering/) 2) it is now easy debuggable, just use this monkey-patch: {noformat} Watir::PageContainer.class_eval {def spawned_click_no_wait_command(command) "ruby -e #{command.inspect}" end} {noformat} Maybe make it even more easier by using $DEBUG and if-statement or something similar? 3) requiring rubygems always, just in case, in the spawned process 4) click_no_wait performs 2-3x faster! It might be possible to improve the performance even more by doing some larger changes with the require statements in watir/core.rb - unfortunately it is not possible anymore to make changes in smaller steps 5) all click_no_wait invocations in unit tests use now development libraries Fixes are within commits: http://github.com/jarmo/watir/commit/7333081e30568ec73eb63f9f75562c2078c55481 http://github.com/jarmo/watir/commit/c71cee1ac820493372d299b8f3a258b497b22e66 simplified debugging and created feature branch for the patches for easier merge > making Element#click_no_wait faster and easier debuggable > --------------------------------------------------------- > > Key: WTR-449 > URL: http://jira.openqa.org/browse/WTR-449 > Project: Watir > Issue Type: Improvement > Components: HTML Controls > Affects Versions: 1.6.5 > Environment: all environments > Reporter: Jarmo Pertman > Priority: Major > > I have been thinking of improving Element#click_no_wait for some time now. I can see the following problems with current solution: > 1) code is not good - method _code_that_copies_readonly_array with funny comment in main namespace, eval_in_spawned_process with TODO and not-TODO comments > 2) users have a lot of problems with click_no_wait (http://bit.ly/asirep) and current code doesn't allow easy debugging with monkey-patching or similar solutions > 3) in the spawned process used for click_no_wait, no rubygems is loaded thus it's possible that users without having RUBYOPT set to -rubygems can't use click_no_wait and since it's hard to debug (see point #2) then they don't even know what's the problem > 4) click_no_wait is just slow because it loads too many files/libraries in it's own process - it should just load all the necessary things and nothing else > 5) currently, in the unit tests click_no_wait process doesn't use development libraries > Here is a benchmark: > *click_no_wait_bench.rb:* > {noformat} > require "rubygems" > require "watir" > require "benchmark" > b = Watir::Browser.new > b.goto "http://www.google.com" > times = 5 > # almost original watir 1.6.5 code > # * added gsub to avoid bug for some ruby versions > # * using ruby instead of start rubyw to measure time > module Watir > module PageContainer > def eval_in_spawned_process(command) > command.strip! > load_path_code = _code_that_copies_readonly_array($LOAD_PATH, '$LOAD_PATH') > ruby_code = "require 'watir/ie'; " > # ruby_code = "$HIDE_IE = #{$HIDE_IE};" # This prevents attaching to a window from setting it visible. However modal dialogs cannot be attached to when not visible. > ruby_code << "pc = #{attach_command}; " # pc = page container > # IDEA: consider changing this to not use instance_eval (it makes the code hard to understand) > ruby_code << "pc.instance_eval(#{command.inspect})" > exec_string = "ruby -e #{(load_path_code + '; ' + ruby_code).inspect}".gsub("\\\"", "'") > system(exec_string) > end > end > end > Benchmark.bmbm do |x| > x.report("watir 1.6.5") {times.times {b.button(:name => "btnG").click_no_wait}} > end > =begin > Rehearsal ----------------------------------------------- > watir 1.6.5 0.031000 0.015000 0.046000 ( 26.136495) > -------------------------------------- total: 0.046000sec > user system total real > watir 1.6.5 0.000000 0.000000 0.000000 ( 23.600350) > =end > # improved section > # * simplified click_no_wait methods > # * requiring rubygems incase of missing RUBYOPT > # * extracted ruby_execute_command into method for easier monkey-patching for debugging and testing reasons > module Watir > class Element > def click_no_wait > assert_enabled > highlight(:set) > element = "#{self.class}.new(#{@page_container.attach_command}, :unique_number, #{self.unique_number})" > @page_container.click_no_wait(element) > highlight(:clear) > end > end > module PageContainer > def click_no_wait(element) > ruby_code = "require 'rubygems';" << > "require 'watir/ie';" << > "#{element}.click!" > system(spawned_click_no_wait_command(ruby_code)) > end > def spawned_click_no_wait_command(command) > "start rubyw -e #{command.inspect}" > end > private :spawned_click_no_wait_command > end > end > Benchmark.bmbm do |x| > x.report("watir improved - ie") {times.times {b.button(:name => "btnG").click_no_wait}} > end > =begin > Rehearsal ------------------------------------------------------- > watir improved - ie 0.032000 0.047000 0.079000 ( 20.141152) > ---------------------------------------------- total: 0.079000sec > user system total real > watir improved - ie 0.047000 0.016000 0.063000 ( 18.931083) > =end > # * loading watir/core.rb to reduce loading of unneeded files/libraries > module Watir > class Element > def click_no_wait > assert_enabled > highlight(:set) > element = "#{self.class}.new(#{@page_container.attach_command}, :unique_number, #{self.unique_number})" > @page_container.click_no_wait(element) > highlight(:clear) > end > end > module PageContainer > def click_no_wait(element) > ruby_code = "require 'rubygems';" << > "require '#{File.expand_path(File.dirname(__FILE__))}/watir/core';" << > "#{element}.click!" > system(spawned_click_no_wait_command(ruby_code)) > end > def spawned_click_no_wait_command(command) > unless $DEBUG > "start rubyw -e #{command.inspect}" > else > puts "#click_no_wait command:" > command = "ruby -e #{command.inspect}" > puts command > command > end > end > private :spawned_click_no_wait_command > end > end > Benchmark.bmbm do |x| > x.report("watir improved - click_no_wait") {times.times {b.button(:name => "btnG").click_no_wait}} > end > =begin > Rehearsal ------------------------------------------------------------------ > watir improved - click_no_wait 0.062000 0.015000 0.077000 ( 9.729557) > --------------------------------------------------------- total: 0.077000sec > user system total real > watir improved - click_no_wait 0.015000 0.047000 0.062000 ( 9.308532) > =end > b.close > {noformat} > *watir/core.rb:* > {noformat} > require 'watir/win32ole' > require 'logger' > require 'watir/exceptions' > require 'watir/matches' > require 'watir/core_ext' > require 'watir/logger' > require 'watir/container' > require 'watir/locator' > require 'watir/page-container' > require 'watir/ie-class' > require 'watir/element' > require 'watir/element_collections' > require 'watir/form' > require 'watir/non_control_elements' > require 'watir/input_elements' > require 'watir/table' > require 'watir/image' > require 'watir/link' > require 'watir/html_element' > require 'watir/waiter' > require 'watir/module' > {noformat} > As it's possible to see from the results then i got click_no_wait to perform faster about 2-3 times (of course this depends on the PC and so on, but these are the results from my machine, which is a quite average laptop)! > Results: > 1) removed all this unnecessary and funny-looking code which also had slight of a "criminal overengineering" smell on it (http://coderoom.wordpress.com/2010/06/23/criminal-overengineering/) > 2) it is now easy to debug #click_no_wait problems: > {noformat} > $DEBUG = true > element.click_no_wait > {noformat} > 3) requiring rubygems always, just in case, in the spawned process > 4) click_no_wait performs 2-3x faster! It might be possible to improve the performance even more by doing some larger changes with the require statements in watir/core.rb - unfortunately it is not possible anymore to make changes in smaller steps > 5) all click_no_wait invocations in unit tests use now development libraries > Fixes are in branch click_no_wait_patch: > http://github.com/jarmo/watir/tree/click_no_wait_patch -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.openqa.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From zeljko.filipin at wa-research.ch Fri Aug 13 11:01:43 2010 From: zeljko.filipin at wa-research.ch (=?UTF-8?Q?=C5=BDeljko_Filipin?=) Date: Fri, 13 Aug 2010 17:01:43 +0200 Subject: [Wtr-development] [wtr-general] Re: Check out the Watir Stack Exchange site! In-Reply-To: References: <97e8febe-77d9-4eb7-a85a-5793525d1490@i28g2000yqa.googlegroups.com> <3c9112da-81fd-4560-9725-091d248f9fc1@w15g2000pro.googlegroups.com> <2562285e-50ee-4405-a865-6c692640b0a2@k39g2000yqb.googlegroups.com> Message-ID: I am giving up on Watir Stack Exchange site (http://bit.ly/watirse). Nobody is voting on the questions. Maybe people are on vacation, or nobody cares. I will concentrate on thinking how to move Watir support to http://stackoverflow.com/ One idea I have: - create a page at watir.com with instructions how to post a question at stackoverflow.com - update http://watir.com/support/ page to say stackoverflow.com is the place for Watir support - send warning message at watir-general that it will be read only for a week - in that week post to watir-general only links to Watir questions at stackoverflow.com - see what happens and decide what to do next Is it too radical? :) ?eljko -------------- next part -------------- An HTML attachment was scrubbed... URL: From alister.scott at gmail.com Fri Aug 13 17:29:21 2010 From: alister.scott at gmail.com (Alister Scott) Date: Sat, 14 Aug 2010 07:29:21 +1000 Subject: [Wtr-development] [wtr-general] Re: Check out the Watir Stack Exchange site! In-Reply-To: References: <97e8febe-77d9-4eb7-a85a-5793525d1490@i28g2000yqa.googlegroups.com> <3c9112da-81fd-4560-9725-091d248f9fc1@w15g2000pro.googlegroups.com> <2562285e-50ee-4405-a865-6c692640b0a2@k39g2000yqb.googlegroups.com> Message-ID: <3597240508589982143@unknownmsgid> I personally don't think what you're proposing is too radical. If people aren't committed, Stack Exchange won't work. I personally dislike the number of complex rules, voting and hierarchy associated with stack exchange stuff. I think it's a bit OTT. I am happy to support any other options you think will work. Cheers, Alister Scott Brisbane, Australia Watir Wiki Master: http://watir.com Blog: http://watirmelon.com Google: http://www.google.com/profiles/alister.scott LinkedIn: http://www.linkedin.com/in/alisterscott On 14/08/2010, at 1:01 AM, "?eljko Filipin" wrote: I am giving up on Watir Stack Exchange site (http://bit.ly/watirse). Nobody is voting on the questions. Maybe people are on vacation, or nobody cares. I will concentrate on thinking how to move Watir support to http://stackoverflow.com/ One idea I have: - create a page at watir.com with instructions how to post a question at stackoverflow.com - update http://watir.com/support/ page to say stackoverflow.com is the place for Watir support - send warning message at watir-general that it will be read only for a week - in that week post to watir-general only links to Watir questions at stackoverflow.com - see what happens and decide what to do next Is it too radical? :) ?eljko _______________________________________________ Wtr-development mailing list Wtr-development at rubyforge.org http://rubyforge.org/mailman/listinfo/wtr-development -------------- next part -------------- An HTML attachment was scrubbed... URL: From simon.m.stewart at gmail.com Sat Aug 14 05:22:01 2010 From: simon.m.stewart at gmail.com (Simon Stewart) Date: Sat, 14 Aug 2010 10:22:01 +0100 Subject: [Wtr-development] 24th August, Selenium developer team meet up Message-ID: Hi, I've had a quick couple of tweets with Charley about this, but perhaps a more formal invitation would be a Good Thing :) The core selenium and webdriver teams will be meeting up on the 24th August for the day on the Google campus. We've extended invitations to the Safari, Chrome, IE, Firefox and Opera development teams to join us. Hopefully at least some of them will come along. The idea is to discuss where the project is, where it's going, meet each other, and get some insight from the browser manufacturers. If any of you would like to come along, please let me know. It'd be great to have you there. We've currently only invited webdriver/selenium devs with commit rights. Simon From watirjira at gmail.com Sat Aug 14 07:33:31 2010 From: watirjira at gmail.com (David Schulberg (JIRA)) Date: Sat, 14 Aug 2010 06:33:31 -0500 (CDT) Subject: [Wtr-development] [JIRA] Commented: (WTR-320) click_no_wait does not work on ruby186-27_rc2 Message-ID: <32921322.347.1281785611549.JavaMail.oqa-j2ee@openqa01.managed.contegix.com> [ http://jira.openqa.org/browse/WTR-320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=19751#action_19751 ] David Schulberg commented on WTR-320: ------------------------------------- I think the low priority on this issue is inappropriate. This issue blocks the prospect of handling javascript popups effectively using watir (refer http://wiki.openqa.org/display/WTR/JavaScript+Pop+Ups?focusedCommentId=43221370#comment-43221370) > click_no_wait does not work on ruby186-27_rc2 > --------------------------------------------- > > Key: WTR-320 > URL: http://jira.openqa.org/browse/WTR-320 > Project: Watir > Issue Type: Bug > Components: Inputs > Affects Versions: 1.6.2 > Environment: Vista SP1 IE8, normal administrator account with default security settings (UAC enabled, IE protected mode enabled) > Reporter: Bill Agee > Fix For: 1.6.5 > > Attachments: patch.txt > > > Several people (including myself) have had problems using click_no_wait on Vista. > The symptom is that the element being clicked will flash yellow, but nothing happens beyond that. The click does not seem to be received. > A patch that solves this problem was posted to the watir dev list, by Derek Berner: > http://rubyforge.org/pipermail/wtr-development/2009-January/000400.html > Looks like the patch was for Windows Server 2008, but it worked for me on Vista SP1 with IE8. > But I tried the same patch on XP SP3, with IE8, and click_no_wait no longer worked. A little work may be required to make sure the patch works on both Vista SP1 and XP. Hopefully Server 2008 and Vista RTM will also both work if Vista SP1 has no problems. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.openqa.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From zeljko.filipin at wa-research.ch Sat Aug 14 08:46:59 2010 From: zeljko.filipin at wa-research.ch (=?UTF-8?Q?=C5=BDeljko_Filipin?=) Date: Sat, 14 Aug 2010 14:46:59 +0200 Subject: [Wtr-development] [wtr-general] Re: Check out the Watir Stack Exchange site! In-Reply-To: <3597240508589982143@unknownmsgid> References: <97e8febe-77d9-4eb7-a85a-5793525d1490@i28g2000yqa.googlegroups.com> <3c9112da-81fd-4560-9725-091d248f9fc1@w15g2000pro.googlegroups.com> <2562285e-50ee-4405-a865-6c692640b0a2@k39g2000yqb.googlegroups.com> <3597240508589982143@unknownmsgid> Message-ID: On Fri, Aug 13, 2010 at 11:29 PM, Alister Scott wrote: > I personally dislike the number of complex rules, voting and hierarchy associated with stack exchange stuff. I agree. I think it is made to create a community around a topic. We already have a community, we just need the software. > I am happy to support any other options you think will work. Stack Overflow is the way to go. Maybe it would be a better idea to set watir-general so all posts are moderated for a week, and in that week just reply to people to ask at Stack Overflow. After a week, we could decide what to do next. ?eljko -------------- next part -------------- An HTML attachment was scrubbed... URL: From watirjira at gmail.com Sat Aug 14 09:25:31 2010 From: watirjira at gmail.com (Jarmo Pertman (JIRA)) Date: Sat, 14 Aug 2010 08:25:31 -0500 (CDT) Subject: [Wtr-development] [JIRA] Commented: (WTR-320) click_no_wait does not work on ruby186-27_rc2 Message-ID: <18087873.354.1281792331619.JavaMail.oqa-j2ee@openqa01.managed.contegix.com> [ http://jira.openqa.org/browse/WTR-320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=19752#action_19752 ] Jarmo Pertman commented on WTR-320: ----------------------------------- I totally agree. I've proposed also another patch for #click_no_wait, which should (in theory) also fix this problem. See at http://jira.openqa.org/browse/WTR-449 Jarmo > click_no_wait does not work on ruby186-27_rc2 > --------------------------------------------- > > Key: WTR-320 > URL: http://jira.openqa.org/browse/WTR-320 > Project: Watir > Issue Type: Bug > Components: Inputs > Affects Versions: 1.6.2 > Environment: Vista SP1 IE8, normal administrator account with default security settings (UAC enabled, IE protected mode enabled) > Reporter: Bill Agee > Fix For: 1.6.5 > > Attachments: patch.txt > > > Several people (including myself) have had problems using click_no_wait on Vista. > The symptom is that the element being clicked will flash yellow, but nothing happens beyond that. The click does not seem to be received. > A patch that solves this problem was posted to the watir dev list, by Derek Berner: > http://rubyforge.org/pipermail/wtr-development/2009-January/000400.html > Looks like the patch was for Windows Server 2008, but it worked for me on Vista SP1 with IE8. > But I tried the same patch on XP SP3, with IE8, and click_no_wait no longer worked. A little work may be required to make sure the patch works on both Vista SP1 and XP. Hopefully Server 2008 and Vista RTM will also both work if Vista SP1 has no problems. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.openqa.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jari.bakken at gmail.com Sat Aug 14 11:52:29 2010 From: jari.bakken at gmail.com (Jari Bakken) Date: Sat, 14 Aug 2010 16:52:29 +0100 Subject: [Wtr-development] 24th August, Selenium developer team meet up In-Reply-To: References: Message-ID: On Sat, Aug 14, 2010 at 10:22 AM, Simon Stewart wrote: > > The core selenium and webdriver teams will be meeting up on the 24th > August for the day on the Google campus. We've extended invitations to > the Safari, Chrome, IE, Firefox and Opera development teams to join > us. Hopefully at least some of them will come along. > I'd of course love to be there, but it's a bit far away :) If there's any way to participate online, I'll make sure to be around for that. Jari From simon.m.stewart at gmail.com Sun Aug 15 08:10:39 2010 From: simon.m.stewart at gmail.com (Simon Stewart) Date: Sun, 15 Aug 2010 13:10:39 +0100 Subject: [Wtr-development] 24th August, Selenium developer team meet up In-Reply-To: References: Message-ID: On Sat, Aug 14, 2010 at 4:52 PM, Jari Bakken wrote: > On Sat, Aug 14, 2010 at 10:22 AM, Simon Stewart > wrote: >> >> The core selenium and webdriver teams will be meeting up on the 24th >> August for the day on the Google campus. We've extended invitations to >> the Safari, Chrome, IE, Firefox and Opera development teams to join >> us. Hopefully at least some of them will come along. >> > > I'd of course love to be there, but it's a bit far away :) If there's > any way to participate online, I'll make sure to be around for that. You're not the first person to ask that. We'll figure out a way to allow remote participants. Probably using Skype unless you can get to a google office. Simon From watirjira at gmail.com Tue Aug 17 09:19:30 2010 From: watirjira at gmail.com (fourchette (JIRA)) Date: Tue, 17 Aug 2010 08:19:30 -0500 (CDT) Subject: [Wtr-development] [JIRA] Commented: (WTR-282) Watir doesn't work on Cygwin [patch] Message-ID: <3756977.391.1282051170765.JavaMail.oqa-j2ee@openqa01.managed.contegix.com> [ http://jira.openqa.org/browse/WTR-282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=19755#action_19755 ] fourchette commented on WTR-282: -------------------------------- reproduced with Windows XP SP3 32bits using environement below $ uname -a CYGWIN_NT-5.1 mtb-p1247630 1.7.6(0.230/5/3) 2010-08-16 16:06 i686 Cygwin $ ruby -v ruby 1.8.7 (2008-08-11 patchlevel 72) [i386-cygwin] $ gem list *** LOCAL GEMS *** activesupport (2.3.8) builder (2.1.2) color (1.4.1) commonwatir (1.6.5) fastercsv (1.5.3) firewatir (1.6.5) hoe (2.6.1) json_pure (1.4.3) nokogiri (1.4.3.1) pdf-writer (1.1.8) rake (0.8.7) rcov (0.9.8) rspec (1.3.0) rubyforge (2.0.4) ruport (1.6.3) s4t-utils (1.0.4) transaction-simple (1.4.0) user-choices (1.1.6.1) watir (1.6.5) win32-api (1.4.6) win32-process (0.6.2) windows-api (0.4.0) windows-pr (1.0.9) wirble (0.1.3) xml-simple (1.0.12) > Watir doesn't work on Cygwin [patch] > ------------------------------------ > > Key: WTR-282 > URL: http://jira.openqa.org/browse/WTR-282 > Project: Watir > Issue Type: Bug > Components: Modal Web Dialog > Affects Versions: 1.6.2 > Environment: WinXP / Cygwin > Reporter: andyl > Priority: Blocker > Fix For: Soon > > > On Cygwin, I ran into two separate problems that prevented Watir 1.6.2 from working. > First, the 'win32ole.so' file that ships with Watir appears to be incompatible with the version that is installed with my copy of Cygwin- > ruby. (see http://pastie.org/374756) > An error message 'bad file permissions' was generated when trying to run 'x = Watir::IE.new' from within IRB. > My workaround was to copy the 'ruby' version of win32ole.so into the 'watir' directories. (see http://pastie.org/374865) > Once this was done, another error occured - relating to modal dialogs. (see http://pastie.org/374865) > This was fixed by commenting out 2 lines in the Watir source code: > File - modal_dialog.rb Line - 65 GetUnknown.call ... > File - win32.rb Line - 6 GetUnknown = Win32API.new(... > Once these lines were commented out, watir worked. > Ideas for fixes: > - Fix the modal dialog issue with conditional execution: > GetUnknown.call (...) unless RUBY_PLATFORM == 'i386-cygwin' > GetUnknown=Win32APUI.new(... unless RUBY_PLATFORM =='i386-cygwin' > > - Fix the win32ole issue by not bundling this file in the gem (Brett thinks maybe it is not needed??) > - Cygwin support: run regression tests on cygwin!! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.openqa.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From watirjira at gmail.com Fri Aug 20 06:28:31 2010 From: watirjira at gmail.com (Aliaksandr Palanetski (JIRA)) Date: Fri, 20 Aug 2010 05:28:31 -0500 (CDT) Subject: [Wtr-development] [JIRA] Created: (WTR-451) implement FireWatir::Element#parent method Message-ID: <8281760.427.1282300111308.JavaMail.oqa-j2ee@openqa01.managed.contegix.com> implement FireWatir::Element#parent method ------------------------------------------ Key: WTR-451 URL: http://jira.openqa.org/browse/WTR-451 Project: Watir Issue Type: New Feature Components: FireWatir, HTML Controls Affects Versions: Someday Environment: WinXP, Linux, Firefox Reporter: Aliaksandr Palanetski Priority: Major implement FireWatir::Element#parent method at the moment it returns empty string -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.openqa.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From watirjira at gmail.com Tue Aug 24 10:47:31 2010 From: watirjira at gmail.com (Jarmo Pertman (JIRA)) Date: Tue, 24 Aug 2010 09:47:31 -0500 (CDT) Subject: [Wtr-development] [JIRA] Created: (WTR-452) adding timeout to #wait Message-ID: <18333447.520.1282661251299.JavaMail.oqa-j2ee@openqa01.managed.contegix.com> adding timeout to #wait ----------------------- Key: WTR-452 URL: http://jira.openqa.org/browse/WTR-452 Project: Watir Issue Type: Improvement Components: Wait Affects Versions: 1.6.5 Environment: all envs Reporter: Jarmo Pertman Currently it is possible that Watir will block forever in it's #wait method under some circumstances. There are questions once in a while in the group also about the timeout of Watir. Unfortunately currently there is no timeout! I have a proposal to add a timeout. And make it hardcoded - let's say 5 minutes. Why hardcoded? Because i think that if your page is unable to load in 5 minutes then your page is broken and should be fixed/changed anyway. This would be a small indicator to the developers and testers that they shouldn't waste so much time of their lives for waiting some bad application to render a page. Charley proposed to create an issue and let people to vote (not downvote) it! So, what do you guys think about making Watir a little as an Opinionated Software as Rails tries to be? (PS, if your page loads more than 5 minutes and you cannot get yourself together to fix it or tell your developers to fix it and you really need to have longer timeouts, then you can always monkey-patch #wait. We're talking about Ruby where everything is possible, remember?) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.openqa.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From zeljko.filipin at wa-research.ch Thu Aug 26 09:41:13 2010 From: zeljko.filipin at wa-research.ch (=?UTF-8?Q?=C5=BDeljko_Filipin?=) Date: Thu, 26 Aug 2010 15:41:13 +0200 Subject: [Wtr-development] Watir Podcast #36: Jarmo Pertman Message-ID: http://watirpodcast.com/36-jarmo-pertman/ ?eljko -- watir.com - community manager watirpodcast.com - host testingpodcast.com - audio podcasts on software testing. all of them vidipodkast.com - pri?amo o hardveru, softveru i ?asopisu Vidi -------------- next part -------------- An HTML attachment was scrubbed... URL: From watirjira at gmail.com Thu Aug 26 14:21:30 2010 From: watirjira at gmail.com (Charley Baker (JIRA)) Date: Thu, 26 Aug 2010 13:21:30 -0500 (CDT) Subject: [Wtr-development] [JIRA] Closed: (WTR-81) Migrate to WET libraries for Win32 support Message-ID: <4870606.610.1282846890782.JavaMail.oqa-j2ee@openqa01.managed.contegix.com> [ http://jira.openqa.org/browse/WTR-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charley Baker closed WTR-81. ---------------------------- Resolution: Incomplete I'm closing this as it's an old report, WET is now a dead library, we need to look into some abstractions around this area, so this is more of a historical note while investigating handling this. > Migrate to WET libraries for Win32 support > ------------------------------------------ > > Key: WTR-81 > URL: http://jira.openqa.org/browse/WTR-81 > Project: Watir > Issue Type: Task > Components: Window Attachment > Affects Versions: 1.4, 1.4.1, 1.5.0/1.5.1 > Reporter: Charley Baker > Assignee: Charley Baker > Priority: Major > Fix For: Soon > > > One of the issues that's arisen as a need is better support for some of the win32 specific window handling. Currently Watir has multiple methods of enumerating windows - calling to Win32OLE shell and iterating through by title as opposed to class which is causing some users issues (WTR-76) and through winClicker.rb. WET has several libraries which can be incorporated into Watir for their OO goodness and stability. It's important to keep the current libraries, given that many users are currently incorporating them into their scripts, however, it would be nice to deprecate them over time. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.openqa.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From watirjira at gmail.com Thu Aug 26 14:25:30 2010 From: watirjira at gmail.com (Charley Baker (JIRA)) Date: Thu, 26 Aug 2010 13:25:30 -0500 (CDT) Subject: [Wtr-development] [JIRA] Commented: (WTR-409) install for 1.6.2 doesn't work after 1.6.5 release Message-ID: <29552752.613.1282847130680.JavaMail.oqa-j2ee@openqa01.managed.contegix.com> [ http://jira.openqa.org/browse/WTR-409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=19778#action_19778 ] Charley Baker commented on WTR-409: ----------------------------------- I'd suggest this scenario is something to consider while moving between versions in the future, but a non starter as a current issue. > install for 1.6.2 doesn't work after 1.6.5 release > -------------------------------------------------- > > Key: WTR-409 > URL: http://jira.openqa.org/browse/WTR-409 > Project: Watir > Issue Type: Bug > Components: Gem installer > Affects Versions: 1.6.2 > Environment: windows > Reporter: Alan Baird > Assignee: Charley Baker > Priority: Critical > Fix For: 1.6.3 > > > This morning I was helping a coworker get some things up and running with watir and noticed that he had inadvertently got 1.6.5. Since 1.6.5 changes the way .visible? works, we decided to go back to 1.6.2 and make sure everything was ok there. We removed watir, commonwatir and firewatir and verified that everything was uninstalled. After that, we did the following: > C:\ >gem install watir -v 1.6.2 > ERROR: Error installing watir: > firewatir requires commonwatir (= 1.6.5, runtime) > C:\ >gem list --local > *** LOCAL GEMS *** > (removed unnecessary gems) > ... > commonwatir (1.6.2) > ... > C:\ >gem install firewatir -v 1.6.2 > Successfully installed firewatir-1.6.2 > 1 gem installed > Installing ri documentation for firewatir-1.6.2... > Installing RDoc documentation for firewatir-1.6.2... > C:\ >gem install watir -v 1.6.2 > Successfully installed watir-1.6.2 > 1 gem installed > Installing ri documentation for watir-1.6.2... > Installing RDoc documentation for watir-1.6.2... > So, to me it seems that there is a gem dependency in the firewatir install for commonwatir 1.6.5 (or maybe it's just the latest version). > What do you think? > Alan > For complete discussion, see http://groups.google.com/group/watir-general/browse_thread/thread/ee8e1abadb533b61?tvc=2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.openqa.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From watirjira at gmail.com Thu Aug 26 14:43:31 2010 From: watirjira at gmail.com (Charley Baker (JIRA)) Date: Thu, 26 Aug 2010 13:43:31 -0500 (CDT) Subject: [Wtr-development] [JIRA] Commented: (WTR-450) Computer will be crashed when ie start In-Reply-To: <7741395.195.1280457871247.JavaMail.oqa-j2ee@openqa01.managed.contegix.com> Message-ID: <21236678.615.1282848211119.JavaMail.oqa-j2ee@openqa01.managed.contegix.com> [ http://jira.openqa.org/browse/WTR-450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=19779#action_19779 ] Charley Baker commented on WTR-450: ----------------------------------- Unless there's more information, this sounds like a non-issue or something isn't worth fixing. I'd recommend closing this. > Computer will be crashed when ie start > -------------------------------------- > > Key: WTR-450 > URL: http://jira.openqa.org/browse/WTR-450 > Project: Watir > Issue Type: Bug > Components: Wait > Affects Versions: 1.6.5 > Environment: MS win xp professional service pack2 > Reporter: ethen.hu > Fix For: 1.6.5 > > > This is my process to show issue when run watir > 1, First Ie6 exist, run watir to create ie instance, ie6 window will be created > 2, But When I update IE6 to IE7, and run watir to create IE instance, In theory, IE7 will be created, Actually, The IE6 window has been created. Now I have update ie6 to ie7, IE6 is not exist; well, watir will > create ie6 window which doesn't work one by one, more than 50 > Now , I found a function named 'window' in ie-process.rb, the condition for return is > "process_id == @process_id", Maybe this is the reason for issue I think. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.openqa.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From watirjira at gmail.com Thu Aug 26 14:45:30 2010 From: watirjira at gmail.com (Charley Baker (JIRA)) Date: Thu, 26 Aug 2010 13:45:30 -0500 (CDT) Subject: [Wtr-development] [JIRA] Commented: (WTR-440) Update AutoIt ActiveX Control library (AutoItX3.dll) bundled with Watir to current version In-Reply-To: <2522252.333.1275579631176.JavaMail.oqa-j2ee@openqa01.managed.contegix.com> Message-ID: <4223950.617.1282848330552.JavaMail.oqa-j2ee@openqa01.managed.contegix.com> [ http://jira.openqa.org/browse/WTR-440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=19780#action_19780 ] Charley Baker commented on WTR-440: ----------------------------------- This is a tough one, since the recommendation is to move away from AutoIT entirely and depend on native calls through win32api, libffi or DL. I'd recommend sitting on this one for now until we resolve that first. Dumping AutoIT for official support is non-trivial. > Update AutoIt ActiveX Control library (AutoItX3.dll) bundled with Watir to current version > -------------------------------------------------------------------------------------------- > > Key: WTR-440 > URL: http://jira.openqa.org/browse/WTR-440 > Project: Watir > Issue Type: Improvement > Components: Gem installer > Affects Versions: 1.6.5 > Environment: Windows all versions > Reporter: Joe DiMauro > > The AutoIt v3 ActiveX Control library (AutoItX3.dll) bundled with Watir1.6.5 is a very old version, (version 3.1.1.0), built back in 2005. > As of 6/1/2010 the version of the library that is distributed with AutoIt's installer is version 3.3.6.1. It contains many improvements, fixes and new commands, functions and features, that could be useful with Watir if it were included, instead of the down-rev version that is currently bundled with Watir. > See AutoIt's change log for details on the changes (from 3.1.1.0 to the current version): > http://www.autoitscript.com/autoit3/docs/history.htm > The current AutoItX3 installer is available as a free download at: > http://www.autoitscript.com/autoit3/index.shtml > There is also a 64-bit version of the library (AutoITX3_x64.dll) that might be of use to install with Watir on 64-bit systems. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.openqa.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From watirjira at gmail.com Thu Aug 26 14:47:30 2010 From: watirjira at gmail.com (Charley Baker (JIRA)) Date: Thu, 26 Aug 2010 13:47:30 -0500 (CDT) Subject: [Wtr-development] [JIRA] Updated: (WTR-439) error using attach method with => syntax In-Reply-To: <2798750.201.1273578510734.JavaMail.oqa-j2ee@openqa01.managed.contegix.com> Message-ID: <24342784.619.1282848450661.JavaMail.oqa-j2ee@openqa01.managed.contegix.com> [ http://jira.openqa.org/browse/WTR-439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charley Baker updated WTR-439: ------------------------------ Priority: Major (was: Minor) Fix Version/s: Next Upgrading this issue, hash should be a valid arg. > error using attach method with => syntax > ---------------------------------------- > > Key: WTR-439 > URL: http://jira.openqa.org/browse/WTR-439 > Project: Watir > Issue Type: Bug > Components: Window Attachment > Affects Versions: 1.6.5 > Environment: Windows XP, IE8 > Reporter: Marc Betts > Priority: Major > Fix For: Next > > > browser.attach(:title=>"title") returns the following error: > ArgumentError: wrong number of arguments (1 for 2) > This works fine using browser.attach(:title, "title") -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.openqa.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From watirjira at gmail.com Thu Aug 26 14:58:30 2010 From: watirjira at gmail.com (Charley Baker (JIRA)) Date: Thu, 26 Aug 2010 13:58:30 -0500 (CDT) Subject: [Wtr-development] [JIRA] Closed: (WTR-431) Template creation In-Reply-To: <21730144.554.1269796236878.JavaMail.oqa-j2ee@openqa01.managed.contegix.com> Message-ID: <18557906.621.1282849110731.JavaMail.oqa-j2ee@openqa01.managed.contegix.com> [ http://jira.openqa.org/browse/WTR-431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charley Baker closed WTR-431. ----------------------------- Just marking closed. > Template creation > ------------------ > > Key: WTR-431 > URL: http://jira.openqa.org/browse/WTR-431 > Project: Watir > Issue Type: New Feature > Components: Other > Affects Versions: Next > Environment: windows xp > Reporter: shanth > > Provide Template creation feature.For e.g If i open a new .rb file it display with pre formatted text that we defined in the template. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.openqa.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From watirjira at gmail.com Thu Aug 26 14:58:30 2010 From: watirjira at gmail.com (Charley Baker (JIRA)) Date: Thu, 26 Aug 2010 13:58:30 -0500 (CDT) Subject: [Wtr-development] [JIRA] Closed: (WTR-430) ie.contains_text returning object id instead of true/false In-Reply-To: <26411997.552.1269795337220.JavaMail.oqa-j2ee@openqa01.managed.contegix.com> Message-ID: <30277284.623.1282849110784.JavaMail.oqa-j2ee@openqa01.managed.contegix.com> [ http://jira.openqa.org/browse/WTR-430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charley Baker closed WTR-430. ----------------------------- > ie.contains_text returning object id instead of true/false > ---------------------------------------------------------- > > Key: WTR-430 > URL: http://jira.openqa.org/browse/WTR-430 > Project: Watir > Issue Type: Bug > Components: Other > Affects Versions: 1.6.5 > Environment: windows xp > Reporter: shanth > > ie.contains_text returning object id instead of true/false -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.openqa.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From watirjira at gmail.com Thu Aug 26 15:00:30 2010 From: watirjira at gmail.com (Charley Baker (JIRA)) Date: Thu, 26 Aug 2010 14:00:30 -0500 (CDT) Subject: [Wtr-development] [JIRA] Closed: (WTR-428) Firefox URL string is always blank In-Reply-To: <21390032.468.1269375217002.JavaMail.oqa-j2ee@openqa01.managed.contegix.com> Message-ID: <21959335.625.1282849230617.JavaMail.oqa-j2ee@openqa01.managed.contegix.com> [ http://jira.openqa.org/browse/WTR-428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charley Baker closed WTR-428. ----------------------------- > Firefox URL string is always blank > ---------------------------------- > > Key: WTR-428 > URL: http://jira.openqa.org/browse/WTR-428 > Project: Watir > Issue Type: Bug > Components: FireWatir > Affects Versions: 1.6.5 > Environment: Watir 1.6.5 > Ruby 1.8.6-p111 > Gem 1.3.6 > Windows 7 > Firefox 3.6 > Reporter: Mark Faust > Priority: Major > Fix For: Next > > > I just installed Watir on a Windows 7 server. Noticed that when using the Firefox browser that the URL string is always blank. The problem seems confined to this one method, as title returns a correct value for any open window. An example irb session follows... > irb(main):014:0> ff.goto "http://yahoo.com" > => # > irb(main):015:0> ff.url > => "" > irb(main):016:0> ff.goto "http://www.google.com" > => # > irb(main):017:0> ff.url > => "" > irb(main):018:0> ff.goto "http://www.mlb.com" > => # > irb(main):019:0> ff.url > => "" > irb(main):020:0> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.openqa.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From watirjira at gmail.com Thu Aug 26 15:02:30 2010 From: watirjira at gmail.com (Charley Baker (JIRA)) Date: Thu, 26 Aug 2010 14:02:30 -0500 (CDT) Subject: [Wtr-development] [JIRA] Closed: (WTR-427) WIN32OLERuntimeErrors on almost every proerty and method In-Reply-To: <5184744.466.1269374737677.JavaMail.oqa-j2ee@openqa01.managed.contegix.com> Message-ID: <31627659.627.1282849350560.JavaMail.oqa-j2ee@openqa01.managed.contegix.com> [ http://jira.openqa.org/browse/WTR-427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charley Baker closed WTR-427. ----------------------------- Resolution: Cannot Reproduce I'm closing due to CNR. Most likely a admin access problem. > WIN32OLERuntimeErrors on almost every proerty and method > -------------------------------------------------------- > > Key: WTR-427 > URL: http://jira.openqa.org/browse/WTR-427 > Project: Watir > Issue Type: Bug > Components: Other > Affects Versions: 1.6.5 > Environment: Watir 1.6.5 > Ruby 1.8.6-p111 > Gem 1.3.6 > Windows 7 Enterprise (version 6.1, build 7600) > Internet Explorer 8 (version 8.0.7600.16385) > Reporter: Mark Faust > Priority: Blocker > > I just installed Watir on a Windows 7 workstation. Almost every operation under IE is returning a WIN32OLERuntimeError for unknown property or method, followed by an error code and an announcement that the interface is unknown or the RPC server is unavailable. The same operations are not problematic under Firefox. This is not occurring after opening and closing many IE windows (a problem that was apparently quite frequent under Win Vista in the past), it occurs with the first window opened. I installed Ruby, updated the Gem and installed Watir as an administrative user. > An example irb session follows: > C:\ruby>irb > irb(main):001:0> require 'Watir' > => true > irb(main):002:0> ie = Watir::IE.new > => # > irb(main):003:0> ie.goto "http://localhost/demo" > => 0.225 > irb(main):004:0> ie.text_field(:name, "username").set "GWashington" > WIN32OLERuntimeError: unknown property or method `document' > HRESULT error code:0x800706b5 > The interface is unknown. > from c:/ruby/lib/ruby/gems/1.8/gems/watir-1.6.5/lib/watir/ie-class.rb:46 > 0:in `method_missing' > from c:/ruby/lib/ruby/gems/1.8/gems/watir-1.6.5/lib/watir/ie-class.rb:46 > 0:in `document' > from c:/ruby/lib/ruby/gems/1.8/gems/watir-1.6.5/lib/watir/container.rb:8 > 00:in `locate_input_element' > from c:/ruby/lib/ruby/gems/1.8/gems/watir-1.6.5/lib/watir/input_elements > .rb:5:in `locate' > from c:/ruby/lib/ruby/gems/1.8/gems/watir-1.6.5/lib/watir/element.rb:53: > in `assert_exists' > from c:/ruby/lib/ruby/gems/1.8/gems/watir-1.6.5/lib/watir/element.rb:288 > :in `enabled?' > from c:/ruby/lib/ruby/gems/1.8/gems/watir-1.6.5/lib/watir/element.rb:60: > in `assert_enabled' > from c:/ruby/lib/ruby/gems/1.8/gems/watir-1.6.5/lib/watir/input_elements > .rb:327:in `set' > from (irb):4 > irb(main):005:0> ie.button(:value, "Login").click > WIN32OLERuntimeError: unknown property or method `document' > HRESULT error code:0x800706b5 > The interface is unknown. > from c:/ruby/lib/ruby/gems/1.8/gems/watir-1.6.5/lib/watir/ie-class.rb:46 > 0:in `method_missing' > from c:/ruby/lib/ruby/gems/1.8/gems/watir-1.6.5/lib/watir/ie-class.rb:46 > 0:in `document' > from c:/ruby/lib/ruby/gems/1.8/gems/watir-1.6.5/lib/watir/container.rb:8 > 00:in `locate_input_element' > from c:/ruby/lib/ruby/gems/1.8/gems/watir-1.6.5/lib/watir/input_elements > .rb:5:in `locate' > from c:/ruby/lib/ruby/gems/1.8/gems/watir-1.6.5/lib/watir/element.rb:53: > in `assert_exists' > from c:/ruby/lib/ruby/gems/1.8/gems/watir-1.6.5/lib/watir/element.rb:288 > :in `enabled?' > from c:/ruby/lib/ruby/gems/1.8/gems/watir-1.6.5/lib/watir/element.rb:60: > in `assert_enabled' > from c:/ruby/lib/ruby/gems/1.8/gems/watir-1.6.5/lib/watir/element.rb:233 > :in `click!' > from c:/ruby/lib/ruby/gems/1.8/gems/watir-1.6.5/lib/watir/element.rb:219 > :in `click' > from (irb):5 > irb(main):006:0> ie.url > WIN32OLERuntimeError: unknown property or method `LocationURL' > HRESULT error code:0x800706b5 > The interface is unknown. > from c:/ruby/lib/ruby/gems/1.8/gems/watir-1.6.5/lib/watir/ie-class.rb:46 > 5:in `method_missing' > from c:/ruby/lib/ruby/gems/1.8/gems/watir-1.6.5/lib/watir/ie-class.rb:46 > 5:in `url' > from (irb):6 > irb(main):007:0> ie.title > WIN32OLERuntimeError: unknown property or method `document' > HRESULT error code:0x800706ba > The RPC server is unavailable. > from c:/ruby/lib/ruby/gems/1.8/gems/watir-1.6.5/lib/watir/ie-class.rb:33 > 9:in `method_missing' > from c:/ruby/lib/ruby/gems/1.8/gems/watir-1.6.5/lib/watir/ie-class.rb:33 > 9:in `title' > from (irb):13 > irb(main):008:0> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.openqa.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From watirjira at gmail.com Thu Aug 26 15:08:30 2010 From: watirjira at gmail.com (Charley Baker (JIRA)) Date: Thu, 26 Aug 2010 14:08:30 -0500 (CDT) Subject: [Wtr-development] [JIRA] Closed: (WTR-423) MySpace Rich Text Comment Box Does not set text (text_field.set) Message-ID: <7250735.629.1282849710577.JavaMail.oqa-j2ee@openqa01.managed.contegix.com> [ http://jira.openqa.org/browse/WTR-423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charley Baker closed WTR-423. ----------------------------- Resolution: Duplicate Closing this issue as a duplicate. Will add a new issue for dealing with js frameworks, but this is more of a documentation issue, possible code changes. > MySpace Rich Text Comment Box Does not set text (text_field.set) > ---------------------------------------------------------------- > > Key: WTR-423 > URL: http://jira.openqa.org/browse/WTR-423 > Project: Watir > Issue Type: Bug > Components: Other > Affects Versions: 1.6.0, 1.6.1, 1.6.2, 1.6.5 > Environment: Windows XP, Ruby 1.8.6 > Reporter: Norm > Priority: Major > > Cannot set text to MySpace's rich text boxes, defined as "textarea" in the source. > To recreate you must sign in to MySpace, attempt to add a comment to a user profile using the following URL: > http://comment.myspace.com/index.cfm?fuseaction=user.viewProfile_commentForm&friendID= > (append the id number of the person you want to comment to the end of the URL). > Next attempt to set the text area such as: > $ie.text_field(:name, /commentText/i).set("this is the text to set") > The text box will not be set with the value. All other text boxes work, for some reason this particular one (rich text?) does not. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.openqa.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From watirjira at gmail.com Thu Aug 26 15:12:30 2010 From: watirjira at gmail.com (Charley Baker (JIRA)) Date: Thu, 26 Aug 2010 14:12:30 -0500 (CDT) Subject: [Wtr-development] [JIRA] Updated: (WTR-422) Need a feature to identify unknown element using inner_text Message-ID: <9882617.631.1282849950573.JavaMail.oqa-j2ee@openqa01.managed.contegix.com> [ http://jira.openqa.org/browse/WTR-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charley Baker updated WTR-422: ------------------------------ Priority: Minor (was: Major) Fix Version/s: Soon Definitely not major priority, though the ability to identify random elements has been coming up a lot lately. Hugh might have a fix for this in the convio branch. > Need a feature to identify unknown element using inner_text > ----------------------------------------------------------- > > Key: WTR-422 > URL: http://jira.openqa.org/browse/WTR-422 > Project: Watir > Issue Type: New Feature > Components: HTML Controls > Affects Versions: 1.6.5 > Environment: IE: Windows > Reporter: Nick Wayne > Fix For: Soon > > > Hi, > It would be really nice if a method is provided to identify any element using inner_text. Right now one has to know the type of element one is looking for to begin with. e.g. div or td or tr. But it is not possible to traverse back from the inner_text and get the element. > e.g. What I am asking for is : > text1 > to be able to get by matching text1 even though I do not know what is the type of is. > Best regards, > Nick -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.openqa.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From watirjira at gmail.com Thu Aug 26 15:14:30 2010 From: watirjira at gmail.com (Charley Baker (JIRA)) Date: Thu, 26 Aug 2010 14:14:30 -0500 (CDT) Subject: [Wtr-development] [JIRA] Updated: (WTR-421) Watir ie.buttons.each does not find > > > WATIR CODE: > ie.buttons.length > #-->0 > ie.buttons[1].exists? > #-->true -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.openqa.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From watirjira at gmail.com Fri Aug 27 13:41:31 2010 From: watirjira at gmail.com (Charley Baker (JIRA)) Date: Fri, 27 Aug 2010 12:41:31 -0500 (CDT) Subject: [Wtr-development] [JIRA] Commented: (WTR-325) Frames with xPath access enhancement for element_by_xpath, elements_by_xpath Message-ID: <3086612.768.1282930891734.JavaMail.oqa-j2ee@openqa01.managed.contegix.com> [ http://jira.openqa.org/browse/WTR-325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=19815#action_19815 ] Charley Baker commented on WTR-325: ----------------------------------- To the original poster, do you have a patch to submit for this? Cheers, Charley > Frames with xPath access enhancement for element_by_xpath, elements_by_xpath > ---------------------------------------------------------------------------- > > Key: WTR-325 > URL: http://jira.openqa.org/browse/WTR-325 > Project: Watir > Issue Type: New Feature > Components: Frame, Xpath Support > Affects Versions: 1.6.2 > Environment: Windows XP, Vista, Server 2008 (all including R2) > IE 7 and 8 > Reporter: U Lwin > Priority: Major > > Watir current release version have limitation with with gathering multiple element information across nested frames. > For ex. > ie.elements_by_xpath() cannot get access across nested frame. > ie.frames().divs and > ie.frames().elements_by_xpath() return function not found > To get by pass that problem I patched frame.rb by adding followings functions from ie-class.rb > tokenize_tagline() > xml_escape() > all_tag_attributes() > html_source() > rexml_document_object() > create_rexml_document_object() > element_by_xpath() > element_by_absolute_xpath() > That solve my problem for accessing access nested frames. Now I can gather links data across nested frames as following.. > left_links = [] > @ie.frame(:name, /CHPDataFrame/i).frame(:name, /LeftPanel/i).frame(:name, /FRAME_ID_ORGANIZER/i).elements_by_xpath("//a[@target='RightPanel']/").each do |lk| > left_links << lk.innertext > end > recommend to patch in next release -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.openqa.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From watirjira at gmail.com Fri Aug 27 13:43:30 2010 From: watirjira at gmail.com (Charley Baker (JIRA)) Date: Fri, 27 Aug 2010 12:43:30 -0500 (CDT) Subject: [Wtr-development] [JIRA] Closed: (WTR-380) JSSH Installation fails on iceweasel 2.0.0 Message-ID: <4502420.771.1282931010640.JavaMail.oqa-j2ee@openqa01.managed.contegix.com> [ http://jira.openqa.org/browse/WTR-380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charley Baker closed WTR-380. ----------------------------- Resolution: Not a problem I'm closing this for now since we do have several successful xpis in the wild as per Anghrez's comment. > JSSH Installation fails on iceweasel 2.0.0 > ------------------------------------------ > > Key: WTR-380 > URL: http://jira.openqa.org/browse/WTR-380 > Project: Watir > Issue Type: Bug > Components: FireWatir > Affects Versions: Open QA Migration > Environment: Linux > Reporter: Zeljko > Assignee: Angrez > > - moved from http://code.google.com/p/firewatir/issues/detail?id=5 > Issue 5: JSSH Installation fails on iceweasel 2.0.0 > 3 people starred this issue and may be notified of changes. > Status: Started > Owner: angrez > Cc: amit.garde, prema.arya > Type-Defect > Priority-Medium > Reported by cwjenks, Mar 09, 2007 > What steps will reproduce the problem? > 1. Install iceweasel and ruby on debian testing > 2. Download jssh-20060221-Linux.xpi and firewatir-1.0.1-mswin32.gem and > save to local drive > 3. Launch iceweasel, open jssh-20060221-Linux.xpi and attempt to install > What is the expected output? > A successfully installed extension! > What do you see instead? > Iceweasel could not install the file at > file:///home/chris/firewatr/jssh-20060221-Linux.xpi > because: Required file does not exist > -214 > What version of the product are you using? On what operating system? > iceweasel 2.0.0 > jssh-20060221-Linux.xpi > firewatir-1.0.1-mswin32.gem > Please provide any additional information below. > Google web and google groups showed only a few, unhelpful messages > mentioning this type of error message, and only for firefox. > --- > Comment 1 by angrez, Mar 11, 2007 > The linux xpi doesn't work as it some of the files are missing in the xpi. I am > working on it to create a correct xpi for Linux. This should be done before our next > release. > Status: Started > Owner: angrez > Cc: amit.garde prema.arya -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.openqa.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From watirjira at gmail.com Fri Aug 27 14:12:30 2010 From: watirjira at gmail.com (Charley Baker (JIRA)) Date: Fri, 27 Aug 2010 13:12:30 -0500 (CDT) Subject: [Wtr-development] [JIRA] Closed: (WTR-382) Can't get jssh to work on mac Message-ID: <30092400.784.1282932750703.JavaMail.oqa-j2ee@openqa01.managed.contegix.com> [ http://jira.openqa.org/browse/WTR-382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charley Baker closed WTR-382. ----------------------------- Resolving and closing. Old issue that appears to be a non starter with our current xpis. There are plenty of other jssh issues which reflect the current state better. > Can't get jssh to work on mac > ----------------------------- > > Key: WTR-382 > URL: http://jira.openqa.org/browse/WTR-382 > Project: Watir > Issue Type: Bug > Components: FireWatir > Affects Versions: Open QA Migration > Environment: Mac > Reporter: Zeljko > > - moved from http://code.google.com/p/firewatir/issues/detail?id=35 > Issue 35: Can't get jssh to work on mac > 3 people starred this issue and may be notified of changes. > Status: New > Owner: ---- > Type-Defect > Priority-Medium > Reported by lisa.crispin, Aug 07, 2007 > What steps will reproduce the problem? > 1. Installed firefox 2.0.0.4 > 2. Installed the plugin jssh-20070312-darwin.xpi > 3. started firefox all of these ways: > ./firefox -P firewatir -jssh > ./firefox-bin -P firewatir -jssh > ./firefox -jssh > 4. telnet localhost 9997 > What is the expected output? What do you see instead? > gets 'connection refused', I expect it to be able to connect > What version of the product are you using? On what operating system? > I haven't installed firewatir yet, because all the instructions I can find > imply that jssh much work first. > Please provide any additional information below. > I've been using Watir on Windows for 3 years, but this is the first time I > tried to get firewatir working on the mac. > --- > Comment 1 by battlehorse, Aug 25, 2007 > The same happens to me. > My firefox version is 2.0.0.6 . > When I try to telnel localhost 9997 i got a 'connection refused' error. > If I check the dialog box under Tools > JSSh , the checkbox 'listen for connections' > is unchecked and the text fields are empty. Even if I check the checkbox and type the > correct port into the textfields, I am not able to apply the changes (the OK button > does not dismiss the dialog, I can only click the 'cancel' button ). > --- > Comment 2 by jmarsan67, Aug 28, 2007 > I've built an extension with the (I think) correct shared lib for Mac that may work. I can provide it to you if you > want to give it a try. > --- > Comment 3 by battlehorse, Aug 28, 2007 > sure. Can you attach the file to this issue or do you prefer sending it to my mail > address ? > > --- > Comment 4 by tinomen, Oct 03, 2007 > I can confirm that the jssh-darwin-0.94.xpi plugin works on my osx 10.4 firefox 2.0.0.7 setup. if someone else > can confirm maybe this can be closed. > --- > Comment 5 by battlehorse, Nov 05, 2007 > I confirm that jssh-darwin-0.94.xpi works too on osx 10.5 and firefox 2.0.0.6 . > --- > Comment 6 by decepticonhearts, Nov 09, 2007 > Exact same problem. System 10.5, Firefox is 2.0.0.9. > --- > Comment 7 by chrisrose.chrisrose, Nov 26, 2007 > I have the same problem also - System 10.4.10, Firefox is 2.0.0.9 > --- > Comment 8 by slauriat, Apr 22, 2008 > I had it work on my first try, running /Applications/Firefox.app/Contents/MacOS/firefox-bin -jssh > The installation docs may just need to get a bit cleaned up? > --- > Comment 9 by lisa.crispin, Apr 22, 2008 > I did get this to work, back when, with Charley's help. But I can't remember anymore > what was the trick. > --- > Comment 10 by zookz... at versanet.de, Apr 30, 2008 > I had the same problems...I found out, that the plugin works well for INTEL macs...It can't be used on PPC macs. > --- > Comment 11 by angrez, Apr 30, 2008 > Can somebody compile Firefox on PC Mac and post the XPI. I don't have access to Mac > OS X machine so just relying on community to provide the XPI > --- > Comment 12 by UshaRani.L, May 21, 2008 > Same issue as Lisa. I have been trying to get FireWatir working on my Mac Leopard. Installed the plugin ssh- > 20070312-darwin.xpi. But doing a "telnet localhost 9997" is giving connection refused. And like battlehorse, I m > not able to submit JSSh configurations. > Could some one give directions on how they got this working on their Intel Mac. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.openqa.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From watirjira at gmail.com Fri Aug 27 14:12:30 2010 From: watirjira at gmail.com (Charley Baker (JIRA)) Date: Fri, 27 Aug 2010 13:12:30 -0500 (CDT) Subject: [Wtr-development] [JIRA] Resolved: (WTR-382) Can't get jssh to work on mac Message-ID: <11062840.782.1282932750668.JavaMail.oqa-j2ee@openqa01.managed.contegix.com> [ http://jira.openqa.org/browse/WTR-382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charley Baker resolved WTR-382. ------------------------------- Resolution: Cannot Reproduce Resolving and closing. Old issue that appears to be a non starter with our current xpis. There are plenty of other jssh issues which reflect the current state better. > Can't get jssh to work on mac > ----------------------------- > > Key: WTR-382 > URL: http://jira.openqa.org/browse/WTR-382 > Project: Watir > Issue Type: Bug > Components: FireWatir > Affects Versions: Open QA Migration > Environment: Mac > Reporter: Zeljko > > - moved from http://code.google.com/p/firewatir/issues/detail?id=35 > Issue 35: Can't get jssh to work on mac > 3 people starred this issue and may be notified of changes. > Status: New > Owner: ---- > Type-Defect > Priority-Medium > Reported by lisa.crispin, Aug 07, 2007 > What steps will reproduce the problem? > 1. Installed firefox 2.0.0.4 > 2. Installed the plugin jssh-20070312-darwin.xpi > 3. started firefox all of these ways: > ./firefox -P firewatir -jssh > ./firefox-bin -P firewatir -jssh > ./firefox -jssh > 4. telnet localhost 9997 > What is the expected output? What do you see instead? > gets 'connection refused', I expect it to be able to connect > What version of the product are you using? On what operating system? > I haven't installed firewatir yet, because all the instructions I can find > imply that jssh much work first. > Please provide any additional information below. > I've been using Watir on Windows for 3 years, but this is the first time I > tried to get firewatir working on the mac. > --- > Comment 1 by battlehorse, Aug 25, 2007 > The same happens to me. > My firefox version is 2.0.0.6 . > When I try to telnel localhost 9997 i got a 'connection refused' error. > If I check the dialog box under Tools > JSSh , the checkbox 'listen for connections' > is unchecked and the text fields are empty. Even if I check the checkbox and type the > correct port into the textfields, I am not able to apply the changes (the OK button > does not dismiss the dialog, I can only click the 'cancel' button ). > --- > Comment 2 by jmarsan67, Aug 28, 2007 > I've built an extension with the (I think) correct shared lib for Mac that may work. I can provide it to you if you > want to give it a try. > --- > Comment 3 by battlehorse, Aug 28, 2007 > sure. Can you attach the file to this issue or do you prefer sending it to my mail > address ? > > --- > Comment 4 by tinomen, Oct 03, 2007 > I can confirm that the jssh-darwin-0.94.xpi plugin works on my osx 10.4 firefox 2.0.0.7 setup. if someone else > can confirm maybe this can be closed. > --- > Comment 5 by battlehorse, Nov 05, 2007 > I confirm that jssh-darwin-0.94.xpi works too on osx 10.5 and firefox 2.0.0.6 . > --- > Comment 6 by decepticonhearts, Nov 09, 2007 > Exact same problem. System 10.5, Firefox is 2.0.0.9. > --- > Comment 7 by chrisrose.chrisrose, Nov 26, 2007 > I have the same problem also - System 10.4.10, Firefox is 2.0.0.9 > --- > Comment 8 by slauriat, Apr 22, 2008 > I had it work on my first try, running /Applications/Firefox.app/Contents/MacOS/firefox-bin -jssh > The installation docs may just need to get a bit cleaned up? > --- > Comment 9 by lisa.crispin, Apr 22, 2008 > I did get this to work, back when, with Charley's help. But I can't remember anymore > what was the trick. > --- > Comment 10 by zookz... at versanet.de, Apr 30, 2008 > I had the same problems...I found out, that the plugin works well for INTEL macs...It can't be used on PPC macs. > --- > Comment 11 by angrez, Apr 30, 2008 > Can somebody compile Firefox on PC Mac and post the XPI. I don't have access to Mac > OS X machine so just relying on community to provide the XPI > --- > Comment 12 by UshaRani.L, May 21, 2008 > Same issue as Lisa. I have been trying to get FireWatir working on my Mac Leopard. Installed the plugin ssh- > 20070312-darwin.xpi. But doing a "telnet localhost 9997" is giving connection refused. And like battlehorse, I m > not able to submit JSSh configurations. > Could some one give directions on how they got this working on their Intel Mac. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.openqa.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From watirjira at gmail.com Fri Aug 27 14:42:30 2010 From: watirjira at gmail.com (Charley Baker (JIRA)) Date: Fri, 27 Aug 2010 13:42:30 -0500 (CDT) Subject: [Wtr-development] [JIRA] Commented: (WTR-323) Remove the check of "readonly" on Text fields Message-ID: <18603713.786.1282934550801.JavaMail.oqa-j2ee@openqa01.managed.contegix.com> [ http://jira.openqa.org/browse/WTR-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=19821#action_19821 ] Charley Baker commented on WTR-323: ----------------------------------- bumping this issue. If you can fork our github repo and submit a pull request, that'd be easiest, http://github.com/bret/watir. > Remove the check of "readonly" on Text fields > --------------------------------------------- > > Key: WTR-323 > URL: http://jira.openqa.org/browse/WTR-323 > Project: Watir > Issue Type: New Feature > Components: Inputs > Affects Versions: 1.6.2 > Environment: Windows XP, IE 8 > Reporter: Markus > Attachments: input_elements.rb > > > I think it is necessary to change a value to a text field even if it's read only. > I change the code in the class input_elements: > # Sets the contents of the text box to the specified text value > # Raises UnknownObjectException if the object cant be found > # Raises ObjectDisabledException if the object is disabled > # Raises ObjectReadOnlyException if the object is read only > def set(value) > assert_enabled > > # assert_not_readonly -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.openqa.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From watirjira at gmail.com Fri Aug 27 14:47:30 2010 From: watirjira at gmail.com (Charley Baker (JIRA)) Date: Fri, 27 Aug 2010 13:47:30 -0500 (CDT) Subject: [Wtr-development] [JIRA] Closed: (WTR-309) Fix timeout errors when starting FireWatir Message-ID: <6572633.790.1282934850650.JavaMail.oqa-j2ee@openqa01.managed.contegix.com> [ http://jira.openqa.org/browse/WTR-309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charley Baker closed WTR-309. ----------------------------- > Fix timeout errors when starting FireWatir > ------------------------------------------ > > Key: WTR-309 > URL: http://jira.openqa.org/browse/WTR-309 > Project: Watir > Issue Type: Bug > Components: FireWatir > Affects Versions: 1.6.2 > Environment: windows > Reporter: Bret Pettichord > Priority: Major > Fix For: Soon > > > Firewatir currently uses the following strategy on startup. > 1. start firefox > 2. sleep 2 seconds > 3. try to connect to jssh, retrying up to three times. > But this is causing intermittent failures. The sleep time is step is configurable, but this isn't really a good choice because it will add a mandatory delay to every start. A better solution would be to poll for the connection immediately and then to time out after 10 or 20 seconds if no connection is made. (This timeout could be configurable, instead of the waittime configuration that is currently supported.) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.openqa.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From watirjira at gmail.com Fri Aug 27 14:47:30 2010 From: watirjira at gmail.com (Charley Baker (JIRA)) Date: Fri, 27 Aug 2010 13:47:30 -0500 (CDT) Subject: [Wtr-development] [JIRA] Resolved: (WTR-309) Fix timeout errors when starting FireWatir Message-ID: <22279146.788.1282934850607.JavaMail.oqa-j2ee@openqa01.managed.contegix.com> [ http://jira.openqa.org/browse/WTR-309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charley Baker resolved WTR-309. ------------------------------- Resolution: Duplicate Dupe, closing. > Fix timeout errors when starting FireWatir > ------------------------------------------ > > Key: WTR-309 > URL: http://jira.openqa.org/browse/WTR-309 > Project: Watir > Issue Type: Bug > Components: FireWatir > Affects Versions: 1.6.2 > Environment: windows > Reporter: Bret Pettichord > Priority: Major > Fix For: Soon > > > Firewatir currently uses the following strategy on startup. > 1. start firefox > 2. sleep 2 seconds > 3. try to connect to jssh, retrying up to three times. > But this is causing intermittent failures. The sleep time is step is configurable, but this isn't really a good choice because it will add a mandatory delay to every start. A better solution would be to poll for the connection immediately and then to time out after 10 or 20 seconds if no connection is made. (This timeout could be configurable, instead of the waittime configuration that is currently supported.) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.openqa.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From watirjira at gmail.com Fri Aug 27 14:59:30 2010 From: watirjira at gmail.com (Charley Baker (JIRA)) Date: Fri, 27 Aug 2010 13:59:30 -0500 (CDT) Subject: [Wtr-development] [JIRA] Resolved: (WTR-283) [Patch] click_no_wait and system call not working on windows server 2003 Message-ID: <7140470.792.1282935570612.JavaMail.oqa-j2ee@openqa01.managed.contegix.com> [ http://jira.openqa.org/browse/WTR-283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charley Baker resolved WTR-283. ------------------------------- Resolution: Duplicate Submitting this as a dup and something the new click no wait code from Jarmo should fix. > [Patch] click_no_wait and system call not working on windows server 2003 > ------------------------------------------------------------------------ > > Key: WTR-283 > URL: http://jira.openqa.org/browse/WTR-283 > Project: Watir > Issue Type: Bug > Components: HTML Controls > Affects Versions: 1.6.2 > Reporter: Charley Baker > Fix For: Soon > > > Reported by Derek Berner: http://rubyforge.org/pipermail/wtr-development/2009-January/000400.html > While working on some tests in our office, we realized click_no_wait > wasn't working at all in Server 2008, due to how the call to "system" > was getting interpreted by the command line. This patch adds a small > tweak to the code that fixes the problem for our platform, and > shouldn't cause any problems in other versions of Windows. > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: watir.patch > Type: text/x-patch > Size: 703 bytes > Desc: not available > URL: -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.openqa.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From watirjira at gmail.com Fri Aug 27 15:01:30 2010 From: watirjira at gmail.com (Charley Baker (JIRA)) Date: Fri, 27 Aug 2010 14:01:30 -0500 (CDT) Subject: [Wtr-development] [JIRA] Closed: (WTR-283) [Patch] click_no_wait and system call not working on windows server 2003 Message-ID: <12448327.794.1282935690538.JavaMail.oqa-j2ee@openqa01.managed.contegix.com> [ http://jira.openqa.org/browse/WTR-283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charley Baker closed WTR-283. ----------------------------- Submitting this as a dup and something the new click no wait code from Jarmo should fix. > [Patch] click_no_wait and system call not working on windows server 2003 > ------------------------------------------------------------------------ > > Key: WTR-283 > URL: http://jira.openqa.org/browse/WTR-283 > Project: Watir > Issue Type: Bug > Components: HTML Controls > Affects Versions: 1.6.2 > Reporter: Charley Baker > Fix For: Soon > > > Reported by Derek Berner: http://rubyforge.org/pipermail/wtr-development/2009-January/000400.html > While working on some tests in our office, we realized click_no_wait > wasn't working at all in Server 2008, due to how the call to "system" > was getting interpreted by the command line. This patch adds a small > tweak to the code that fixes the problem for our platform, and > shouldn't cause any problems in other versions of Windows. > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: watir.patch > Type: text/x-patch > Size: 703 bytes > Desc: not available > URL: -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.openqa.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From watirjira at gmail.com Fri Aug 27 15:03:30 2010 From: watirjira at gmail.com (Ethan (JIRA)) Date: Fri, 27 Aug 2010 14:03:30 -0500 (CDT) Subject: [Wtr-development] [JIRA] Commented: (WTR-323) Remove the check of "readonly" on Text fields Message-ID: <4541817.796.1282935810601.JavaMail.oqa-j2ee@openqa01.managed.contegix.com> [ http://jira.openqa.org/browse/WTR-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=19825#action_19825 ] Ethan commented on WTR-323: --------------------------- it looks like the only change here is to comment the line assert_not_readonly in the set method. (text formatting munged the # character into an ordered list). I do not think that this should be changed; the point is to simulate user interaction and a user can't set a readonly field. There are simple enough workarounds for this, like element.ole_object.value="whatever" which will bypass the readonly check. the #set method, however, should perform the check. > Remove the check of "readonly" on Text fields > --------------------------------------------- > > Key: WTR-323 > URL: http://jira.openqa.org/browse/WTR-323 > Project: Watir > Issue Type: New Feature > Components: Inputs > Affects Versions: 1.6.2 > Environment: Windows XP, IE 8 > Reporter: Markus > Attachments: input_elements.rb > > > I think it is necessary to change a value to a text field even if it's read only. > I change the code in the class input_elements: > # Sets the contents of the text box to the specified text value > # Raises UnknownObjectException if the object cant be found > # Raises ObjectDisabledException if the object is disabled > # Raises ObjectReadOnlyException if the object is read only > def set(value) > assert_enabled > > # assert_not_readonly -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.openqa.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From watirjira at gmail.com Fri Aug 27 15:09:30 2010 From: watirjira at gmail.com (Charley Baker (JIRA)) Date: Fri, 27 Aug 2010 14:09:30 -0500 (CDT) Subject: [Wtr-development] [JIRA] Closed: (WTR-263) Loading Firefox takes 2 seconds. This time can be reduced by removing sleep. [patch] Message-ID: <24806893.798.1282936170662.JavaMail.oqa-j2ee@openqa01.managed.contegix.com> [ http://jira.openqa.org/browse/WTR-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charley Baker closed WTR-263. ----------------------------- Resolution: Cannot Reproduce I'm closing this one, the code has changed a lot and no longer seeing this. > Loading Firefox takes 2 seconds. This time can be reduced by removing sleep. [patch] > ------------------------------------------------------------------------------------ > > Key: WTR-263 > URL: http://jira.openqa.org/browse/WTR-263 > Project: Watir > Issue Type: Improvement > Components: FireWatir > Affects Versions: 1.6.2 > Environment: Winxp, Firefox 3, firewatir 1.2.1 > Reporter: Tony > Fix For: Next > > > When loading firefox, it waits for 2 seconds. > This time can be reduced by removing the sleep in the initialize functions and increasing the tries in set_defaults() > The tries in the default, will keep trying to connect to the jssh telnet n number of times. > Hence this works out to be faster. > code remains mostly the same .. just the last few lines of the initialize function is changed. > Below are the 2 lines > #sleep waitTime ## commented this line > set_defaults(500) #added 500 to the set_defaults.. it will try to connect 500 times and then stop > Code modified - > module FireWatir > class Firefox > def initialize(options = {}) > if(options.kind_of?(Integer)) > options = {:waitTime => options} > end > if(options[:profile]) > profile_opt = "-P #{options[:profile]}" > else > profile_opt = "" > end > puts "PROFILE: #{profile_opt}" > waitTime = options[:waitTime] || 2 > if(RUBY_PLATFORM =~ /.*mswin.*/) > #puts "plaftorm is windows" > # Get the path to Firefox.exe using Registry. > require 'win32/registry.rb' > path_to_exe = "" > Win32::Registry::HKEY_LOCAL_MACHINE.open('SOFTWARE\Mozilla\Mozilla Firefox') do |reg| > keys = reg.keys > reg1 = Win32::Registry::HKEY_LOCAL_MACHINE.open("SOFTWARE\\Mozilla\\Mozilla Firefox\\#{keys[0]}\\Main") > reg1.each do |subkey, type, data| > if(subkey =~ /pathtoexe/i) > path_to_exe = data > end > end > end > puts "Starting Firefox using the executable : #{path_to_exe}" > puts "Waiting for #{waitTime} seconds for Firefox to get started." > @t = Thread.new { system("\"#{path_to_exe}\" -jssh #{profile_opt}") } > elsif(RUBY_PLATFORM =~ /linux/i) > puts RUBY_PLATFORM > path_to_bin = `which firefox`.strip > puts "#{path_to_bin} -jssh #{profile_opt}" > @t = Thread.new { `#{path_to_bin} -jssh #{profile_opt}` } > end > > #sleep waitTime ## commented this line > > set_defaults(500) #added 500 to the set_defaults.. it will try to connect 500 times and then stop > get_window_number() > set_browser_document() > end -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.openqa.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From watirjira at gmail.com Fri Aug 27 15:12:30 2010 From: watirjira at gmail.com (Charley Baker (JIRA)) Date: Fri, 27 Aug 2010 14:12:30 -0500 (CDT) Subject: [Wtr-development] [JIRA] Closed: (WTR-259) Winclicker - no effect after update was done Message-ID: <10967842.800.1282936350579.JavaMail.oqa-j2ee@openqa01.managed.contegix.com> [ http://jira.openqa.org/browse/WTR-259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charley Baker closed WTR-259. ----------------------------- Resolution: Cannot Reproduce Old code, old problem, a lot of other solutions have popped up in the meantime. > Winclicker - no effect after update was done > -------------------------------------------- > > Key: WTR-259 > URL: http://jira.openqa.org/browse/WTR-259 > Project: Watir > Issue Type: Bug > Affects Versions: 1.5.6 > Environment: watir 1.5.6 (latest watir and ruby version which can be updated from the net) > Reporter: GEA > Priority: Major > Fix For: Future > > > I used the following code > def myclick(button, waitTime = 3) > w = WinClicker.new > longName = $ie.dir.gsub("/" , "\\" ) > shortName = w.getShortFileName(longName) > c = "start ruby #{shortName}\\watir\\clickJSDialog.rb #{button} > #{waitTime} " > puts "Starting #{c}" > w.winsystem(c) > w=nil > end > Then, before the button i want to click that generates the popup, added: myclick ("Ok",3) > But after I updated the ruby it doesn't have any effect. Another command page is opened but it disappears very quickly, maybe is an > error there but can't be seen. The IE wasn't changed in the mean time. > Is this a bug? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.openqa.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From watirjira at gmail.com Fri Aug 27 15:19:30 2010 From: watirjira at gmail.com (Jarmo Pertman (JIRA)) Date: Fri, 27 Aug 2010 14:19:30 -0500 (CDT) Subject: [Wtr-development] [JIRA] Commented: (WTR-323) Remove the check of "readonly" on Text fields Message-ID: <4248335.802.1282936770559.JavaMail.oqa-j2ee@openqa01.managed.contegix.com> [ http://jira.openqa.org/browse/WTR-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=19828#action_19828 ] Jarmo Pertman commented on WTR-323: ----------------------------------- Agreed with Ethan. Also, you can use directly #value method. > Remove the check of "readonly" on Text fields > --------------------------------------------- > > Key: WTR-323 > URL: http://jira.openqa.org/browse/WTR-323 > Project: Watir > Issue Type: New Feature > Components: Inputs > Affects Versions: 1.6.2 > Environment: Windows XP, IE 8 > Reporter: Markus > Attachments: input_elements.rb > > > I think it is necessary to change a value to a text field even if it's read only. > I change the code in the class input_elements: > # Sets the contents of the text box to the specified text value > # Raises UnknownObjectException if the object cant be found > # Raises ObjectDisabledException if the object is disabled > # Raises ObjectReadOnlyException if the object is read only > def set(value) > assert_enabled > > # assert_not_readonly -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.openqa.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From watirjira at gmail.com Fri Aug 27 15:41:31 2010 From: watirjira at gmail.com (Charley Baker (JIRA)) Date: Fri, 27 Aug 2010 14:41:31 -0500 (CDT) Subject: [Wtr-development] [JIRA] Closed: (WTR-323) Remove the check of "readonly" on Text fields Message-ID: <28041807.804.1282938091088.JavaMail.oqa-j2ee@openqa01.managed.contegix.com> [ http://jira.openqa.org/browse/WTR-323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charley Baker closed WTR-323. ----------------------------- Resolution: Won't Fix Closing this due to comments above. Possible with existing calls, and generally not recommended. > Remove the check of "readonly" on Text fields > --------------------------------------------- > > Key: WTR-323 > URL: http://jira.openqa.org/browse/WTR-323 > Project: Watir > Issue Type: New Feature > Components: Inputs > Affects Versions: 1.6.2 > Environment: Windows XP, IE 8 > Reporter: Markus > Attachments: input_elements.rb > > > I think it is necessary to change a value to a text field even if it's read only. > I change the code in the class input_elements: > # Sets the contents of the text box to the specified text value > # Raises UnknownObjectException if the object cant be found > # Raises ObjectDisabledException if the object is disabled > # Raises ObjectReadOnlyException if the object is read only > def set(value) > assert_enabled > > # assert_not_readonly -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.openqa.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From watirjira at gmail.com Fri Aug 27 17:02:31 2010 From: watirjira at gmail.com (Jarmo Pertman (JIRA)) Date: Fri, 27 Aug 2010 16:02:31 -0500 (CDT) Subject: [Wtr-development] [JIRA] Commented: (WTR-436) All Elements should allow String locator, which will be used as an :id In-Reply-To: <2079608.150.1273275570443.JavaMail.oqa-j2ee@openqa01.managed.contegix.com> Message-ID: <7763654.806.1282942951297.JavaMail.oqa-j2ee@openqa01.managed.contegix.com> [ http://jira.openqa.org/browse/WTR-436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=19830#action_19830 ] Jarmo Pertman commented on WTR-436: ----------------------------------- I agree. > All Elements should allow String locator, which will be used as an :id > ---------------------------------------------------------------------- > > Key: WTR-436 > URL: http://jira.openqa.org/browse/WTR-436 > Project: Watir > Issue Type: New Feature > Components: Other > Affects Versions: 2.0 > Environment: any > Reporter: Jarmo Pertman > > Selenium has a lot of different ways of locating elements. This is > not what i would like to see in > Watir and as i understand then most of you in here also think like > that. But i think that it would > be great if ALL elements would accept one String as an identifier, > which would be used to locate an > element by id. No exceptions - it would be the > same for every element. > For example: > b.text_field("blah").set "my text" # would search text fields with ID and if not found > # would raise an exception > Most of the time i'm finding myself to use ID to locate > elements, which means that my tests are full of method(:id => 'xxxx'). > Would be great if there would be less code. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.openqa.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From watirjira at gmail.com Fri Aug 27 17:06:30 2010 From: watirjira at gmail.com (Jarmo Pertman (JIRA)) Date: Fri, 27 Aug 2010 16:06:30 -0500 (CDT) Subject: [Wtr-development] [JIRA] Resolved: (WTR-449) making Element#click_no_wait faster and easier debuggable In-Reply-To: <16766026.183.1280354011131.JavaMail.oqa-j2ee@openqa01.managed.contegix.com> Message-ID: <30676005.808.1282943190619.JavaMail.oqa-j2ee@openqa01.managed.contegix.com> [ http://jira.openqa.org/browse/WTR-449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarmo Pertman resolved WTR-449. ------------------------------- Resolution: Fixed merged into master > making Element#click_no_wait faster and easier debuggable > --------------------------------------------------------- > > Key: WTR-449 > URL: http://jira.openqa.org/browse/WTR-449 > Project: Watir > Issue Type: Improvement > Components: HTML Controls > Affects Versions: 1.6.5 > Environment: all environments > Reporter: Jarmo Pertman > Priority: Major > > I have been thinking of improving Element#click_no_wait for some time now. I can see the following problems with current solution: > 1) code is not good - method _code_that_copies_readonly_array with funny comment in main namespace, eval_in_spawned_process with TODO and not-TODO comments > 2) users have a lot of problems with click_no_wait (http://bit.ly/asirep) and current code doesn't allow easy debugging with monkey-patching or similar solutions > 3) in the spawned process used for click_no_wait, no rubygems is loaded thus it's possible that users without having RUBYOPT set to -rubygems can't use click_no_wait and since it's hard to debug (see point #2) then they don't even know what's the problem > 4) click_no_wait is just slow because it loads too many files/libraries in it's own process - it should just load all the necessary things and nothing else > 5) currently, in the unit tests click_no_wait process doesn't use development libraries > Here is a benchmark: > *click_no_wait_bench.rb:* > {noformat} > require "rubygems" > require "watir" > require "benchmark" > b = Watir::Browser.new > b.goto "http://www.google.com" > times = 5 > # almost original watir 1.6.5 code > # * added gsub to avoid bug for some ruby versions > # * using ruby instead of start rubyw to measure time > module Watir > module PageContainer > def eval_in_spawned_process(command) > command.strip! > load_path_code = _code_that_copies_readonly_array($LOAD_PATH, '$LOAD_PATH') > ruby_code = "require 'watir/ie'; " > # ruby_code = "$HIDE_IE = #{$HIDE_IE};" # This prevents attaching to a window from setting it visible. However modal dialogs cannot be attached to when not visible. > ruby_code << "pc = #{attach_command}; " # pc = page container > # IDEA: consider changing this to not use instance_eval (it makes the code hard to understand) > ruby_code << "pc.instance_eval(#{command.inspect})" > exec_string = "ruby -e #{(load_path_code + '; ' + ruby_code).inspect}".gsub("\\\"", "'") > system(exec_string) > end > end > end > Benchmark.bmbm do |x| > x.report("watir 1.6.5") {times.times {b.button(:name => "btnG").click_no_wait}} > end > =begin > Rehearsal ----------------------------------------------- > watir 1.6.5 0.031000 0.015000 0.046000 ( 26.136495) > -------------------------------------- total: 0.046000sec > user system total real > watir 1.6.5 0.000000 0.000000 0.000000 ( 23.600350) > =end > # improved section > # * simplified click_no_wait methods > # * requiring rubygems incase of missing RUBYOPT > # * extracted ruby_execute_command into method for easier monkey-patching for debugging and testing reasons > module Watir > class Element > def click_no_wait > assert_enabled > highlight(:set) > element = "#{self.class}.new(#{@page_container.attach_command}, :unique_number, #{self.unique_number})" > @page_container.click_no_wait(element) > highlight(:clear) > end > end > module PageContainer > def click_no_wait(element) > ruby_code = "require 'rubygems';" << > "require 'watir/ie';" << > "#{element}.click!" > system(spawned_click_no_wait_command(ruby_code)) > end > def spawned_click_no_wait_command(command) > "start rubyw -e #{command.inspect}" > end > private :spawned_click_no_wait_command > end > end > Benchmark.bmbm do |x| > x.report("watir improved - ie") {times.times {b.button(:name => "btnG").click_no_wait}} > end > =begin > Rehearsal ------------------------------------------------------- > watir improved - ie 0.032000 0.047000 0.079000 ( 20.141152) > ---------------------------------------------- total: 0.079000sec > user system total real > watir improved - ie 0.047000 0.016000 0.063000 ( 18.931083) > =end > # * loading watir/core.rb to reduce loading of unneeded files/libraries > module Watir > class Element > def click_no_wait > assert_enabled > highlight(:set) > element = "#{self.class}.new(#{@page_container.attach_command}, :unique_number, #{self.unique_number})" > @page_container.click_no_wait(element) > highlight(:clear) > end > end > module PageContainer > def click_no_wait(element) > ruby_code = "require 'rubygems';" << > "require '#{File.expand_path(File.dirname(__FILE__))}/watir/core';" << > "#{element}.click!" > system(spawned_click_no_wait_command(ruby_code)) > end > def spawned_click_no_wait_command(command) > unless $DEBUG > "start rubyw -e #{command.inspect}" > else > puts "#click_no_wait command:" > command = "ruby -e #{command.inspect}" > puts command > command > end > end > private :spawned_click_no_wait_command > end > end > Benchmark.bmbm do |x| > x.report("watir improved - click_no_wait") {times.times {b.button(:name => "btnG").click_no_wait}} > end > =begin > Rehearsal ------------------------------------------------------------------ > watir improved - click_no_wait 0.062000 0.015000 0.077000 ( 9.729557) > --------------------------------------------------------- total: 0.077000sec > user system total real > watir improved - click_no_wait 0.015000 0.047000 0.062000 ( 9.308532) > =end > b.close > {noformat} > *watir/core.rb:* > {noformat} > require 'watir/win32ole' > require 'logger' > require 'watir/exceptions' > require 'watir/matches' > require 'watir/core_ext' > require 'watir/logger' > require 'watir/container' > require 'watir/locator' > require 'watir/page-container' > require 'watir/ie-class' > require 'watir/element' > require 'watir/element_collections' > require 'watir/form' > require 'watir/non_control_elements' > require 'watir/input_elements' > require 'watir/table' > require 'watir/image' > require 'watir/link' > require 'watir/html_element' > require 'watir/waiter' > require 'watir/module' > {noformat} > As it's possible to see from the results then i got click_no_wait to perform faster about 2-3 times (of course this depends on the PC and so on, but these are the results from my machine, which is a quite average laptop)! > Results: > 1) removed all this unnecessary and funny-looking code which also had slight of a "criminal overengineering" smell on it (http://coderoom.wordpress.com/2010/06/23/criminal-overengineering/) > 2) it is now easy to debug #click_no_wait problems: > {noformat} > $DEBUG = true > element.click_no_wait > {noformat} > 3) requiring rubygems always, just in case, in the spawned process > 4) click_no_wait performs 2-3x faster! It might be possible to improve the performance even more by doing some larger changes with the require statements in watir/core.rb - unfortunately it is not possible anymore to make changes in smaller steps > 5) all click_no_wait invocations in unit tests use now development libraries > Fixes are in branch click_no_wait_patch: > http://github.com/jarmo/watir/tree/click_no_wait_patch -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.openqa.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From watirjira at gmail.com Fri Aug 27 17:06:30 2010 From: watirjira at gmail.com (Jarmo Pertman (JIRA)) Date: Fri, 27 Aug 2010 16:06:30 -0500 (CDT) Subject: [Wtr-development] [JIRA] Closed: (WTR-449) making Element#click_no_wait faster and easier debuggable In-Reply-To: <16766026.183.1280354011131.JavaMail.oqa-j2ee@openqa01.managed.contegix.com> Message-ID: <17916199.810.1282943190656.JavaMail.oqa-j2ee@openqa01.managed.contegix.com> [ http://jira.openqa.org/browse/WTR-449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarmo Pertman closed WTR-449. ----------------------------- > making Element#click_no_wait faster and easier debuggable > --------------------------------------------------------- > > Key: WTR-449 > URL: http://jira.openqa.org/browse/WTR-449 > Project: Watir > Issue Type: Improvement > Components: HTML Controls > Affects Versions: 1.6.5 > Environment: all environments > Reporter: Jarmo Pertman > Priority: Major > > I have been thinking of improving Element#click_no_wait for some time now. I can see the following problems with current solution: > 1) code is not good - method _code_that_copies_readonly_array with funny comment in main namespace, eval_in_spawned_process with TODO and not-TODO comments > 2) users have a lot of problems with click_no_wait (http://bit.ly/asirep) and current code doesn't allow easy debugging with monkey-patching or similar solutions > 3) in the spawned process used for click_no_wait, no rubygems is loaded thus it's possible that users without having RUBYOPT set to -rubygems can't use click_no_wait and since it's hard to debug (see point #2) then they don't even know what's the problem > 4) click_no_wait is just slow because it loads too many files/libraries in it's own process - it should just load all the necessary things and nothing else > 5) currently, in the unit tests click_no_wait process doesn't use development libraries > Here is a benchmark: > *click_no_wait_bench.rb:* > {noformat} > require "rubygems" > require "watir" > require "benchmark" > b = Watir::Browser.new > b.goto "http://www.google.com" > times = 5 > # almost original watir 1.6.5 code > # * added gsub to avoid bug for some ruby versions > # * using ruby instead of start rubyw to measure time > module Watir > module PageContainer > def eval_in_spawned_process(command) > command.strip! > load_path_code = _code_that_copies_readonly_array($LOAD_PATH, '$LOAD_PATH') > ruby_code = "require 'watir/ie'; " > # ruby_code = "$HIDE_IE = #{$HIDE_IE};" # This prevents attaching to a window from setting it visible. However modal dialogs cannot be attached to when not visible. > ruby_code << "pc = #{attach_command}; " # pc = page container > # IDEA: consider changing this to not use instance_eval (it makes the code hard to understand) > ruby_code << "pc.instance_eval(#{command.inspect})" > exec_string = "ruby -e #{(load_path_code + '; ' + ruby_code).inspect}".gsub("\\\"", "'") > system(exec_string) > end > end > end > Benchmark.bmbm do |x| > x.report("watir 1.6.5") {times.times {b.button(:name => "btnG").click_no_wait}} > end > =begin > Rehearsal ----------------------------------------------- > watir 1.6.5 0.031000 0.015000 0.046000 ( 26.136495) > -------------------------------------- total: 0.046000sec > user system total real > watir 1.6.5 0.000000 0.000000 0.000000 ( 23.600350) > =end > # improved section > # * simplified click_no_wait methods > # * requiring rubygems incase of missing RUBYOPT > # * extracted ruby_execute_command into method for easier monkey-patching for debugging and testing reasons > module Watir > class Element > def click_no_wait > assert_enabled > highlight(:set) > element = "#{self.class}.new(#{@page_container.attach_command}, :unique_number, #{self.unique_number})" > @page_container.click_no_wait(element) > highlight(:clear) > end > end > module PageContainer > def click_no_wait(element) > ruby_code = "require 'rubygems';" << > "require 'watir/ie';" << > "#{element}.click!" > system(spawned_click_no_wait_command(ruby_code)) > end > def spawned_click_no_wait_command(command) > "start rubyw -e #{command.inspect}" > end > private :spawned_click_no_wait_command > end > end > Benchmark.bmbm do |x| > x.report("watir improved - ie") {times.times {b.button(:name => "btnG").click_no_wait}} > end > =begin > Rehearsal ------------------------------------------------------- > watir improved - ie 0.032000 0.047000 0.079000 ( 20.141152) > ---------------------------------------------- total: 0.079000sec > user system total real > watir improved - ie 0.047000 0.016000 0.063000 ( 18.931083) > =end > # * loading watir/core.rb to reduce loading of unneeded files/libraries > module Watir > class Element > def click_no_wait > assert_enabled > highlight(:set) > element = "#{self.class}.new(#{@page_container.attach_command}, :unique_number, #{self.unique_number})" > @page_container.click_no_wait(element) > highlight(:clear) > end > end > module PageContainer > def click_no_wait(element) > ruby_code = "require 'rubygems';" << > "require '#{File.expand_path(File.dirname(__FILE__))}/watir/core';" << > "#{element}.click!" > system(spawned_click_no_wait_command(ruby_code)) > end > def spawned_click_no_wait_command(command) > unless $DEBUG > "start rubyw -e #{command.inspect}" > else > puts "#click_no_wait command:" > command = "ruby -e #{command.inspect}" > puts command > command > end > end > private :spawned_click_no_wait_command > end > end > Benchmark.bmbm do |x| > x.report("watir improved - click_no_wait") {times.times {b.button(:name => "btnG").click_no_wait}} > end > =begin > Rehearsal ------------------------------------------------------------------ > watir improved - click_no_wait 0.062000 0.015000 0.077000 ( 9.729557) > --------------------------------------------------------- total: 0.077000sec > user system total real > watir improved - click_no_wait 0.015000 0.047000 0.062000 ( 9.308532) > =end > b.close > {noformat} > *watir/core.rb:* > {noformat} > require 'watir/win32ole' > require 'logger' > require 'watir/exceptions' > require 'watir/matches' > require 'watir/core_ext' > require 'watir/logger' > require 'watir/container' > require 'watir/locator' > require 'watir/page-container' > require 'watir/ie-class' > require 'watir/element' > require 'watir/element_collections' > require 'watir/form' > require 'watir/non_control_elements' > require 'watir/input_elements' > require 'watir/table' > require 'watir/image' > require 'watir/link' > require 'watir/html_element' > require 'watir/waiter' > require 'watir/module' > {noformat} > As it's possible to see from the results then i got click_no_wait to perform faster about 2-3 times (of course this depends on the PC and so on, but these are the results from my machine, which is a quite average laptop)! > Results: > 1) removed all this unnecessary and funny-looking code which also had slight of a "criminal overengineering" smell on it (http://coderoom.wordpress.com/2010/06/23/criminal-overengineering/) > 2) it is now easy to debug #click_no_wait problems: > {noformat} > $DEBUG = true > element.click_no_wait > {noformat} > 3) requiring rubygems always, just in case, in the spawned process > 4) click_no_wait performs 2-3x faster! It might be possible to improve the performance even more by doing some larger changes with the require statements in watir/core.rb - unfortunately it is not possible anymore to make changes in smaller steps > 5) all click_no_wait invocations in unit tests use now development libraries > Fixes are in branch click_no_wait_patch: > http://github.com/jarmo/watir/tree/click_no_wait_patch -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.openqa.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From watirjira at gmail.com Fri Aug 27 17:26:30 2010 From: watirjira at gmail.com (Charley Baker (JIRA)) Date: Fri, 27 Aug 2010 16:26:30 -0500 (CDT) Subject: [Wtr-development] [JIRA] Closed: (WTR-436) All Elements should allow String locator, which will be used as an :id In-Reply-To: <2079608.150.1273275570443.JavaMail.oqa-j2ee@openqa01.managed.contegix.com> Message-ID: <1153291.812.1282944390668.JavaMail.oqa-j2ee@openqa01.managed.contegix.com> [ http://jira.openqa.org/browse/WTR-436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charley Baker closed WTR-436. ----------------------------- Resolution: Not a problem Closing based on choice #1, seconded and thirded. :) > All Elements should allow String locator, which will be used as an :id > ---------------------------------------------------------------------- > > Key: WTR-436 > URL: http://jira.openqa.org/browse/WTR-436 > Project: Watir > Issue Type: New Feature > Components: Other > Affects Versions: 2.0 > Environment: any > Reporter: Jarmo Pertman > > Selenium has a lot of different ways of locating elements. This is > not what i would like to see in > Watir and as i understand then most of you in here also think like > that. But i think that it would > be great if ALL elements would accept one String as an identifier, > which would be used to locate an > element by id. No exceptions - it would be the > same for every element. > For example: > b.text_field("blah").set "my text" # would search text fields with ID and if not found > # would raise an exception > Most of the time i'm finding myself to use ID to locate > elements, which means that my tests are full of method(:id => 'xxxx'). > Would be great if there would be less code. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.openqa.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From watirjira at gmail.com Sat Aug 28 05:09:32 2010 From: watirjira at gmail.com (Jarmo Pertman (JIRA)) Date: Sat, 28 Aug 2010 04:09:32 -0500 (CDT) Subject: [Wtr-development] [JIRA] Reopened: (WTR-436) All Elements should allow String locator, which will be used as an :id In-Reply-To: <2079608.150.1273275570443.JavaMail.oqa-j2ee@openqa01.managed.contegix.com> Message-ID: <753137.815.1282986572084.JavaMail.oqa-j2ee@openqa01.managed.contegix.com> [ http://jira.openqa.org/browse/WTR-436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarmo Pertman reopened WTR-436: ------------------------------- How can you close it if the further actions are not clear nor done? What are the further actions? Is the single argument code going to be deleted and a note put into the releasenotes or is there some other plan (for example, display a warning that single argument is deprecated and then in the next version delete the code itself)? Reopening it since the further actions are not clear (at least to me). > All Elements should allow String locator, which will be used as an :id > ---------------------------------------------------------------------- > > Key: WTR-436 > URL: http://jira.openqa.org/browse/WTR-436 > Project: Watir > Issue Type: New Feature > Components: Other > Affects Versions: 2.0 > Environment: any > Reporter: Jarmo Pertman > > Selenium has a lot of different ways of locating elements. This is > not what i would like to see in > Watir and as i understand then most of you in here also think like > that. But i think that it would > be great if ALL elements would accept one String as an identifier, > which would be used to locate an > element by id. No exceptions - it would be the > same for every element. > For example: > b.text_field("blah").set "my text" # would search text fields with ID and if not found > # would raise an exception > Most of the time i'm finding myself to use ID to locate > elements, which means that my tests are full of method(:id => 'xxxx'). > Would be great if there would be less code. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.openqa.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From paul.rogers at shaw.ca Sun Aug 29 21:52:46 2010 From: paul.rogers at shaw.ca (Paul Rogers) Date: Sun, 29 Aug 2010 19:52:46 -0600 Subject: [Wtr-development] Fwd: Watir Advertising In-Reply-To: <20100824124730.4r7k61i1usosgcw4@box580.bluehost.com> References: <20100824124730.4r7k61i1usosgcw4@box580.bluehost.com> Message-ID: any thoughts? Paul ---------- Forwarded message ---------- From: Date: Tue, Aug 24, 2010 at 12:47 PM Subject: Watir Advertising To: paul.rogers at shaw.ca Hi Paul, I came across your site and I found it really interesting. The reason I'm contacting you today is that a client of mine is looking to advertise and I thought your website would be a great fit. I was wondering whether you had any advertising opportunities available? Thanks, Alexia -------------- next part -------------- An HTML attachment was scrubbed... URL: From watirjira at gmail.com Mon Aug 30 08:11:30 2010 From: watirjira at gmail.com (Zeljko (JIRA)) Date: Mon, 30 Aug 2010 07:11:30 -0500 (CDT) Subject: [Wtr-development] [JIRA] Commented: (WTR-258) New Screen Capture Code Message-ID: <12078295.824.1283170290967.JavaMail.oqa-j2ee@openqa01.managed.contegix.com> [ http://jira.openqa.org/browse/WTR-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=19834#action_19834 ] Zeljko commented on WTR-258: ---------------------------- I this this should be removed from Watir, since it is "just" a browser driver. If people need screen shots, there is a gem for that. > New Screen Capture Code > ----------------------- > > Key: WTR-258 > URL: http://jira.openqa.org/browse/WTR-258 > Project: Watir > Issue Type: Improvement > Components: Other > Affects Versions: 1.6.5 > Environment: win32 > Reporter: Bret Pettichord > Priority: Major > Fix For: Soon > > > From: Heesob Park > Date: Tue, Sep 30, 2008 at 12:43 AM > Subject: Re: screen capture to display it or to save it to a file possible? > To: ruby-talk ML > 2008/9/30 liketofindoutwhy : > > On Sep 28, 1:46 pm, Tim Hunter wrote: > >> liketofindoutwhy wrote: > >> > On Sep 28, 11:29 am, liketofindoutwhy > >> > wrote: > >> >> i would like do screencaptureand then to display it in that app's > >> >> window, or be able to save the file in hard disk as a GIF or PNG. I > >> >> wonder if TCL Ruby or RMagick can already do that? Thanks. > >> > >> > oh i actually mean Ruby/Tk > >> > >> RMagick can do it on systems that have X Window. In other words, not MS > >> Windows.http://studio.imagemagick.org/RMagick/doc/image1.html#capture. > > > > hm... so can you install x-window capabilities on XP or Vista... will > > that work? I think the Cygwin install x-window capabilities on > > Windows. > > > > > > > There is screen_capture method in watir. But it is unstable. > Here is the revised screen_capture method for Windows: > require 'win32ole' > require 'Win32API' > def screen_capture(filename, active_window_only=false) > keybd_event = Win32API.new("user32", "keybd_event", ['I','I','L','L'], 'V') > openClipboard = Win32API.new('user32', 'OpenClipboard', ['L'], 'I') > setClipboardData = Win32API.new('user32', 'SetClipboardData', ['I', 'I'], 'I') > closeClipboard = Win32API.new('user32', 'CloseClipboard', [], 'I') > globalAlloc = Win32API.new('kernel32', 'GlobalAlloc', ['I', 'I'], 'I') > globalLock = Win32API.new('kernel32', 'GlobalLock', ['I'], 'I') > globalUnlock = Win32API.new('kernel32', 'GlobalUnlock', ['I'], 'I') > memcpy = Win32API.new('msvcrt', 'memcpy', ['I', 'P', 'I'], 'I') > wsh = WIN32OLE.new('Wscript.Shell') > if not active_window_only > keybd_event.Call(0x2C,0,0,0) # Print Screen > else > keybd_event.Call(0x2C,1,0,0) # Alt+Print Screen > end > exec = wsh.Exec('mspaint.exe') > wsh.AppActivate(exec.ProcessID) > sleep(1) > # Ctrl + V : Paste > wsh.SendKeys("^v") > sleep(1) > # Alt F + A : Save As > wsh.SendKeys("%fa") > # copy filename to clipboard > hmem = globalAlloc.Call(0x0002, filename.length+1) > mem = globalLock.Call(hmem) > memcpy.Call(mem, filename, filename.length+1) > globalUnlock.Call(hmem) > openClipboard.Call(0) > setClipboardData.Call(1, hmem) > closeClipboard.Call > sleep(1) > # Ctrl + V : Paste > wsh.SendKeys("^v") > if filename[/\.gif/i] > wsh.SendKeys("{TAB}g") > elsif filename[/\.jpg/i] > wsh.SendKeys("{TAB}j") > end > wsh.SendKeys("~") # enter > sleep(1) > wsh.SendKeys("yy") > sleep(4) > exec.Terminate > end > screen_capture("c:\\test.gif") > Regards, > Park Heesob -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.openqa.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From watirjira at gmail.com Mon Aug 30 08:22:30 2010 From: watirjira at gmail.com (Zeljko (JIRA)) Date: Mon, 30 Aug 2010 07:22:30 -0500 (CDT) Subject: [Wtr-development] [JIRA] Commented: (WTR-436) All Elements should allow String locator, which will be used as an :id In-Reply-To: <2079608.150.1273275570443.JavaMail.oqa-j2ee@openqa01.managed.contegix.com> Message-ID: <26221829.826.1283170950857.JavaMail.oqa-j2ee@openqa01.managed.contegix.com> [ http://jira.openqa.org/browse/WTR-436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=19835#action_19835 ] Zeljko commented on WTR-436: ---------------------------- I think #3 (leave it as is) is the next action, maybe #1 in the future (deprecate the single argument API entirely). > All Elements should allow String locator, which will be used as an :id > ---------------------------------------------------------------------- > > Key: WTR-436 > URL: http://jira.openqa.org/browse/WTR-436 > Project: Watir > Issue Type: New Feature > Components: Other > Affects Versions: 2.0 > Environment: any > Reporter: Jarmo Pertman > > Selenium has a lot of different ways of locating elements. This is > not what i would like to see in > Watir and as i understand then most of you in here also think like > that. But i think that it would > be great if ALL elements would accept one String as an identifier, > which would be used to locate an > element by id. No exceptions - it would be the > same for every element. > For example: > b.text_field("blah").set "my text" # would search text fields with ID and if not found > # would raise an exception > Most of the time i'm finding myself to use ID to locate > elements, which means that my tests are full of method(:id => 'xxxx'). > Would be great if there would be less code. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.openqa.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From charley.baker at gmail.com Mon Aug 30 17:35:04 2010 From: charley.baker at gmail.com (Charley Baker) Date: Mon, 30 Aug 2010 15:35:04 -0600 Subject: [Wtr-development] Fwd: Watir Advertising In-Reply-To: References: <20100824124730.4r7k61i1usosgcw4@box580.bluehost.com> Message-ID: Are you talking in terms of the Watir.com site? -c On Sun, Aug 29, 2010 at 7:52 PM, Paul Rogers wrote: > any thoughts? > Paul > > ---------- Forwarded message ---------- > From: > Date: Tue, Aug 24, 2010 at 12:47 PM > Subject: Watir Advertising > To: paul.rogers at shaw.ca > > > Hi Paul, > > I came across your site and I found it really interesting. The reason I'm > contacting you today is that a client of mine is looking to advertise and I > thought your website would be a great fit. I was wondering whether you had > any advertising opportunities available? > > Thanks, > Alexia > > > > > _______________________________________________ > Wtr-development mailing list > Wtr-development at rubyforge.org > http://rubyforge.org/mailman/listinfo/wtr-development > From paul.rogers at shaw.ca Mon Aug 30 18:21:28 2010 From: paul.rogers at shaw.ca (Paul Rogers) Date: Mon, 30 Aug 2010 16:21:28 -0600 Subject: [Wtr-development] Fwd: Watir Advertising In-Reply-To: References: <20100824124730.4r7k61i1usosgcw4@box580.bluehost.com> Message-ID: I guess so. On Mon, Aug 30, 2010 at 3:35 PM, Charley Baker wrote: > Are you talking in terms of the Watir.com site? > > -c > > On Sun, Aug 29, 2010 at 7:52 PM, Paul Rogers wrote: > > any thoughts? > > Paul > > > > ---------- Forwarded message ---------- > > From: > > Date: Tue, Aug 24, 2010 at 12:47 PM > > Subject: Watir Advertising > > To: paul.rogers at shaw.ca > > > > > > Hi Paul, > > > > I came across your site and I found it really interesting. The reason I'm > > contacting you today is that a client of mine is looking to advertise and > I > > thought your website would be a great fit. I was wondering whether you > had > > any advertising opportunities available? > > > > Thanks, > > Alexia > > > > > > > > > > _______________________________________________ > > Wtr-development mailing list > > Wtr-development at rubyforge.org > > http://rubyforge.org/mailman/listinfo/wtr-development > > > _______________________________________________ > Wtr-development mailing list > Wtr-development at rubyforge.org > http://rubyforge.org/mailman/listinfo/wtr-development > -------------- next part -------------- An HTML attachment was scrubbed... URL: From zeljko.filipin at wa-research.ch Tue Aug 31 06:00:39 2010 From: zeljko.filipin at wa-research.ch (=?UTF-8?Q?=C5=BDeljko_Filipin?=) Date: Tue, 31 Aug 2010 12:00:39 +0200 Subject: [Wtr-development] Fwd: Watir Advertising In-Reply-To: References: <20100824124730.4r7k61i1usosgcw4@box580.bluehost.com> Message-ID: Since watir.com is hosted on wordpress.com, we can not put any ads there (or maybe I got it wrong): http://en.support.wordpress.com/advertising/ We should move watir.com to a hosted solution if we wanted to serve ads. Moving is not a problem actually, I have a shared server with a few wordpress installs, and one more would not hurt. We had a discussion while back about advertisements and I guess the conclusion was that we do not need the money. :) We get some money from donations, and the costs for running the project are really low. Just out of curiosity, do you know what would be advertised, and how much money would we get? ?eljko -------------- next part -------------- An HTML attachment was scrubbed... URL: From zeljko.filipin at wa-research.ch Tue Aug 31 06:16:15 2010 From: zeljko.filipin at wa-research.ch (=?UTF-8?Q?=C5=BDeljko_Filipin?=) Date: Tue, 31 Aug 2010 12:16:15 +0200 Subject: [Wtr-development] Watir at Wikipedia Message-ID: There is an article on Watir at Wikipedia [1]. I have decided to clean it up, because it was out of date. If anybody has a minute, please take a look, fix something, or let me know what should be fixed. Thanks, ?eljko -- [1] http://en.wikipedia.org/wiki/Watir -------------- next part -------------- An HTML attachment was scrubbed... URL: From zeljko.filipin at wa-research.ch Tue Aug 31 07:24:38 2010 From: zeljko.filipin at wa-research.ch (=?UTF-8?Q?=C5=BDeljko_Filipin?=) Date: Tue, 31 Aug 2010 13:24:38 +0200 Subject: [Wtr-development] Watir in Scheme! Message-ID: http://code.google.com/p/win-control/ ?eljko -- watir.com - community manager watirpodcast.com - host testingpodcast.com - audio podcasts on software testing. all of them vidipodkast.com - pri?amo o hardveru, softveru i ?asopisu Vidi -------------- next part -------------- An HTML attachment was scrubbed... URL: From watirjira at gmail.com Tue Aug 31 09:39:31 2010 From: watirjira at gmail.com (Alan Baird (JIRA)) Date: Tue, 31 Aug 2010 08:39:31 -0500 (CDT) Subject: [Wtr-development] [JIRA] Commented: (WTR-452) adding timeout to #wait In-Reply-To: <18333447.520.1282661251299.JavaMail.oqa-j2ee@openqa01.managed.contegix.com> Message-ID: <8222583.831.1283261971110.JavaMail.oqa-j2ee@openqa01.managed.contegix.com> [ http://jira.openqa.org/browse/WTR-452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=19836#action_19836 ] Alan Baird commented on WTR-452: -------------------------------- Jarmo - I think I would be generally for adding a timeout to wait, but I think that it should be configurable. Just because Rails is opinionated doesn't mean Watir has to be. This seems like trying to attempt to impose best practices on testing which isn't a good idea for an automation suite that is applied to all different kinds of contexts. On principle, Watir should not be opinionated. This reminds me of a discussion where somebody said a tester should not try to code around an ID that was not unique on a page. Yes, it's a violation of good practice, but it seems almost as ignored as it is followed. In this case, or in others, testers that have "fought the good fight" to get to use Watir in the first place will have one more point of contention to deal with in talking to people that might have opposed the adoption of the tool in the first place. Not everyone has a good relationship with their developers, and sometimes this is completely out of their control despite their best efforts. We should not impose any more restrictions than we have to on our users that are fighting uphill battles just to be able to use open source software in the first place. I don't think that adding a configurable timeout to this function should be a big deal. I can imagine scenarios where dealing with additional complexity is not something that should be done in Waitr, but I don't think this is one of those instances. Is there a reason why having a configurable timeout would be problematic? Alan (PS - sorry if this is on the soapbox a bit, but I think the reasons are still valid) > adding timeout to #wait > ----------------------- > > Key: WTR-452 > URL: http://jira.openqa.org/browse/WTR-452 > Project: Watir > Issue Type: Improvement > Components: Wait > Affects Versions: 1.6.5 > Environment: all envs > Reporter: Jarmo Pertman > > Currently it is possible that Watir will block forever in it's #wait method under some circumstances. There are questions once in a while in the group also about the timeout of Watir. > Unfortunately currently there is no timeout! > I have a proposal to add a timeout. And make it hardcoded - let's say 5 minutes. Why hardcoded? Because i think that if your page is unable to load in 5 minutes then your page is broken and should be fixed/changed anyway. This would be a small indicator to the developers and testers that they shouldn't waste so much time of their lives for waiting some bad application to render a page. > Charley proposed to create an issue and let people to vote (not downvote) it! > So, what do you guys think about making Watir a little as an Opinionated Software as Rails tries to be? > (PS, if your page loads more than 5 minutes and you cannot get yourself together to fix it or tell your developers to fix it and you really need to have longer timeouts, then you can always monkey-patch #wait. We're talking about Ruby where everything is possible, remember?) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.openqa.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From watirjira at gmail.com Tue Aug 31 12:15:31 2010 From: watirjira at gmail.com (Jarmo Pertman (JIRA)) Date: Tue, 31 Aug 2010 11:15:31 -0500 (CDT) Subject: [Wtr-development] [JIRA] Commented: (WTR-452) adding timeout to #wait In-Reply-To: <18333447.520.1282661251299.JavaMail.oqa-j2ee@openqa01.managed.contegix.com> Message-ID: <24491056.833.1283271331259.JavaMail.oqa-j2ee@openqa01.managed.contegix.com> [ http://jira.openqa.org/browse/WTR-452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=19837#action_19837 ] Jarmo Pertman commented on WTR-452: ----------------------------------- Again, i personally feel that 5 minutes is more than enough and if some page for some reason doesn't load in that time then there are more important problems to deal with than not-configurable-timeout-setting-in-watir :) If tester doesn't open up a bug right at that point in fear of the developers or whoever then that tester shouldn't be a tester at all. I would let him/her go immediately if i would be in charge. Tester should not be quiet or think "oh, i'm not gonna bother anyone with this small detail, because everyone has already a lot of work to do - just let it be that slow". Tester should act to make those changes. If tester is afraid to talk with developers directly, address them through manager instead. If that is also a problem, well, i think there are then just too much problems already and that particular tester should consider a career change. There is 2 reasons why not having a configurable timeout: 1) So pages would be fixed instead of ignoring the problem 2) The less configuration options the better. Why is iPhone so popular? Not because it's so good (it isn't :P), but because it is so easy to use and you just don't have to (and can't) configure too much. Again, if it is really-really-really needed to increase the timeout, then just go through the trouble to monkey-patch the code :P Also wanted to say that currently Firewatir has already a 5 minute timeout implemented. Don't know since when. Should this be changed also? Sorry if i sounded too straightforward and/or harsh. > adding timeout to #wait > ----------------------- > > Key: WTR-452 > URL: http://jira.openqa.org/browse/WTR-452 > Project: Watir > Issue Type: Improvement > Components: Wait > Affects Versions: 1.6.5 > Environment: all envs > Reporter: Jarmo Pertman > > Currently it is possible that Watir will block forever in it's #wait method under some circumstances. There are questions once in a while in the group also about the timeout of Watir. > Unfortunately currently there is no timeout! > I have a proposal to add a timeout. And make it hardcoded - let's say 5 minutes. Why hardcoded? Because i think that if your page is unable to load in 5 minutes then your page is broken and should be fixed/changed anyway. This would be a small indicator to the developers and testers that they shouldn't waste so much time of their lives for waiting some bad application to render a page. > Charley proposed to create an issue and let people to vote (not downvote) it! > So, what do you guys think about making Watir a little as an Opinionated Software as Rails tries to be? > (PS, if your page loads more than 5 minutes and you cannot get yourself together to fix it or tell your developers to fix it and you really need to have longer timeouts, then you can always monkey-patch #wait. We're talking about Ruby where everything is possible, remember?) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.openqa.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From watirjira at gmail.com Tue Aug 31 14:49:30 2010 From: watirjira at gmail.com (fourchette (JIRA)) Date: Tue, 31 Aug 2010 13:49:30 -0500 (CDT) Subject: [Wtr-development] [JIRA] Created: (WTR-453) firewatir dones work with cygwin because it can locate firefox executable Message-ID: <21820430.835.1283280570684.JavaMail.oqa-j2ee@openqa01.managed.contegix.com> firewatir dones work with cygwin because it can locate firefox executable ------------------------------------------------------------------------- Key: WTR-453 URL: http://jira.openqa.org/browse/WTR-453 Project: Watir Issue Type: Bug Components: Documentation Affects Versions: 1.6.5 Environment: $ gem search watir *** LOCAL GEMS *** commonwatir (1.6.5) firewatir (1.6.5) watir (1.6.5) $ gem env RubyGems Environment: - RUBYGEMS VERSION: 1.3.7 - RUBY VERSION: 1.8.7 (2008-08-11 patchlevel 72) [i386-cygwin] - INSTALLATION DIRECTORY: /usr/lib/ruby/gems/1.8 - RUBY EXECUTABLE: /usr/bin/ruby.exe - EXECUTABLE DIRECTORY: /usr/bin - RUBYGEMS PLATFORMS: - ruby - x86-cygwin - GEM PATHS: - /usr/lib/ruby/gems/1.8 - /home/Alexis/.gem/ruby/1.8 - GEM CONFIGURATION: - :update_sources => true - :verbose => true - :benchmark => false - :backtrace => false - :bulk_threshold => 1000 - REMOTE SOURCES: - http://rubygems.org/ $ Reporter: fourchette if you try to run the example provided on watir example page using firefox and cygwin it just does not work #!/usr/bin/ruby # Here we see a very simple WATIR script to drive to google and validate a page require 'rubygems' require 'watir' # use watir gem test_site = 'http://www.google.com' # set a variable Watir::Browser.default = 'firefox' b = Watir::Browser.new # open the IE browser b.goto(test_site) # load url, go to site b.text_field(:name, "q").set("pickaxe") # load text "pickaxe" into search field named "q" b.button(:name, "btnG").click # "btnG" is the name of the Search button, click it if b.text.include?("Programming Ruby") puts "Test Passed. Found the test string: 'Programming Ruby'." else puts "Test Failed! Could not find: 'Programming Ruby'" end ____________ $ ruby watir_test.rb /usr/lib/ruby/gems/1.8/gems/firewatir-1.6.5/lib/firewatir/firefox.rb:1010:in `current_os': undefined local variable or method `plateform' for # (NameError) from /usr/lib/ruby/gems/1.8/gems/firewatir-1.6.5/lib/firewatir/firefox.rb:124:in `initialize' from /usr/lib/ruby/gems/1.8/gems/commonwatir-1.6.5/lib/watir/browser.rb:65:in `new' from /usr/lib/ruby/gems/1.8/gems/commonwatir-1.6.5/lib/watir/browser.rb:65:in `new' from watir_test.rb:8 $ the reason for that is because around line 1000 in /usr/lib/ruby/gems/1.8/gems/firewatir-1.6.5/lib/firewatir/firefox.rb the variable platform == 'i386-cygwin', so it can't get caught by select/case right below. all you need to change is at firefox.rb:1000 from when /mingw32|mswin|windows/i to when /mingw32|mswin|windows|cygwin/i and that's it. nothing else. $ ruby watir_test.rb sh: C:Program: command not found Test Failed! Could not find: 'Programming Ruby' $ (actually the example fails because i have google in french, but it does work i dont know what the sh: C:Program: command not found is doing in the output (and no the -w is not active, it vomits ugly things otherwise :)) it would be great to push this change in the next firewatir release so that it actually supports cywin -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.openqa.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From charley.baker at gmail.com Tue Aug 31 15:31:54 2010 From: charley.baker at gmail.com (Charley Baker) Date: Tue, 31 Aug 2010 13:31:54 -0600 Subject: [Wtr-development] Fwd: Watir Advertising In-Reply-To: References: <20100824124730.4r7k61i1usosgcw4@box580.bluehost.com> Message-ID: Honestly, it would be nice to have a bit more money. I'm assuming the current money has gone to hosting on watir.com? I can think of a few things right off the bat that would be helpful - stickers, tshirts and other promotional "stuff", slices and build machines so we can make sure the tests are running in CI, I think watirbuild is dead, money to sponsor some of the testing and open source confs. We're doing ok, but it would be nice to have some help to keep things going well and make even bigger inroads. Selenium has had the backing of google among others, Watir has been a grass roots project, but could benefit from some infusion of cash and/or resources. In the talks I've given on Watir, I've payed my own way, but that does come with a cost. Charley Baker Lead Developer, Watir, http://watir.com On Tue, Aug 31, 2010 at 4:00 AM, ?eljko Filipin wrote: > Since watir.com is hosted on wordpress.com, we can not put any ads there (or > maybe I got it wrong): > > http://en.support.wordpress.com/advertising/ > > We should move watir.com to a hosted solution if we wanted to serve ads. > > Moving is not a problem actually, I have a shared server with a few > wordpress installs, and one more would not hurt. > > We had a discussion while back about advertisements and I guess the > conclusion was that we do not need the money. :) We get some money from > donations, and the costs for running the project are really low. > > Just out of curiosity, do you know what would be advertised, and how much > money would we get? > > ?eljko > > _______________________________________________ > Wtr-development mailing list > Wtr-development at rubyforge.org > http://rubyforge.org/mailman/listinfo/wtr-development > From watirjira at gmail.com Tue Aug 31 15:44:30 2010 From: watirjira at gmail.com (fourchette (JIRA)) Date: Tue, 31 Aug 2010 14:44:30 -0500 (CDT) Subject: [Wtr-development] [JIRA] Commented: (WTR-282) Watir doesn't work on Cygwin [patch] Message-ID: <7920023.837.1283283870822.JavaMail.oqa-j2ee@openqa01.managed.contegix.com> [ http://jira.openqa.org/browse/WTR-282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=19838#action_19838 ] fourchette commented on WTR-282: -------------------------------- thanks andy, your suggestion worked ! so 1. replace the win32ole.so file so it matches the default ruby one 2. add the : unless RUBY_PLATFORM == 'i386-cygwin' at File - win32.rb Line - 6 GetUnknown = Win32API.new(... and the default Watir example works (didn't need the other line update, maybe it will resurface later when i more seriously use watir) watir team : please run tests on cygwin too :) > Watir doesn't work on Cygwin [patch] > ------------------------------------ > > Key: WTR-282 > URL: http://jira.openqa.org/browse/WTR-282 > Project: Watir > Issue Type: Bug > Components: Modal Web Dialog > Affects Versions: 1.6.2 > Environment: WinXP / Cygwin > Reporter: andyl > Priority: Blocker > Fix For: Soon > > > On Cygwin, I ran into two separate problems that prevented Watir 1.6.2 from working. > First, the 'win32ole.so' file that ships with Watir appears to be incompatible with the version that is installed with my copy of Cygwin- > ruby. (see http://pastie.org/374756) > An error message 'bad file permissions' was generated when trying to run 'x = Watir::IE.new' from within IRB. > My workaround was to copy the 'ruby' version of win32ole.so into the 'watir' directories. (see http://pastie.org/374865) > Once this was done, another error occured - relating to modal dialogs. (see http://pastie.org/374865) > This was fixed by commenting out 2 lines in the Watir source code: > File - modal_dialog.rb Line - 65 GetUnknown.call ... > File - win32.rb Line - 6 GetUnknown = Win32API.new(... > Once these lines were commented out, watir worked. > Ideas for fixes: > - Fix the modal dialog issue with conditional execution: > GetUnknown.call (...) unless RUBY_PLATFORM == 'i386-cygwin' > GetUnknown=Win32APUI.new(... unless RUBY_PLATFORM =='i386-cygwin' > > - Fix the win32ole issue by not bundling this file in the gem (Brett thinks maybe it is not needed??) > - Cygwin support: run regression tests on cygwin!! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.openqa.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From paul.rogers at shaw.ca Tue Aug 31 16:55:06 2010 From: paul.rogers at shaw.ca (Paul Rogers) Date: Tue, 31 Aug 2010 14:55:06 -0600 Subject: [Wtr-development] Fwd: Watir Advertising In-Reply-To: References: <20100824124730.4r7k61i1usosgcw4@box580.bluehost.com> Message-ID: let me ask that guy what he would be advertising and how much it would cost. Of course the cash we may get from advertsising just go to hosting costs :-( On Tue, Aug 31, 2010 at 1:31 PM, Charley Baker wrote: > Honestly, it would be nice to have a bit more money. I'm assuming the > current money has gone to hosting on watir.com? I can think of a few > things right off the bat that would be helpful - stickers, tshirts and > other promotional "stuff", slices and build machines so we can make > sure the tests are running in CI, I think watirbuild is dead, money to > sponsor some of the testing and open source confs. > > We're doing ok, but it would be nice to have some help to keep > things going well and make even bigger inroads. Selenium has had the > backing of google among others, Watir has been a grass roots project, > but could benefit from some infusion of cash and/or resources. In the > talks I've given on Watir, I've payed my own way, but that does come > with a cost. > > Charley Baker > Lead Developer, Watir, http://watir.com > > > > On Tue, Aug 31, 2010 at 4:00 AM, ?eljko Filipin > wrote: > > Since watir.com is hosted on wordpress.com, we can not put any ads there > (or > > maybe I got it wrong): > > > > http://en.support.wordpress.com/advertising/ > > > > We should move watir.com to a hosted solution if we wanted to serve ads. > > > > Moving is not a problem actually, I have a shared server with a few > > wordpress installs, and one more would not hurt. > > > > We had a discussion while back about advertisements and I guess the > > conclusion was that we do not need the money. :) We get some money from > > donations, and the costs for running the project are really low. > > > > Just out of curiosity, do you know what would be advertised, and how much > > money would we get? > > > > ?eljko > > > > _______________________________________________ > > Wtr-development mailing list > > Wtr-development at rubyforge.org > > http://rubyforge.org/mailman/listinfo/wtr-development > > > _______________________________________________ > Wtr-development mailing list > Wtr-development at rubyforge.org > http://rubyforge.org/mailman/listinfo/wtr-development > -------------- next part -------------- An HTML attachment was scrubbed... URL: From zeljko.filipin at wa-research.ch Tue Aug 31 17:40:14 2010 From: zeljko.filipin at wa-research.ch (=?UTF-8?Q?=C5=BDeljko_Filipin?=) Date: Tue, 31 Aug 2010 23:40:14 +0200 Subject: [Wtr-development] Fwd: Watir Advertising In-Reply-To: References: <20100824124730.4r7k61i1usosgcw4@box580.bluehost.com> Message-ID: 2010/8/31 Paul Rogers > Of course the cash we may get from advertsising just go to hosting costs :-( If we decide to take ads, I will host watir.com. I do not think it will bring my cheap shared hosting down. :) Please do ask for details. ?eljko -------------- next part -------------- An HTML attachment was scrubbed... URL: From zeljko.filipin at wa-research.ch Tue Aug 31 18:08:34 2010 From: zeljko.filipin at wa-research.ch (=?UTF-8?Q?=C5=BDeljko_Filipin?=) Date: Wed, 1 Sep 2010 00:08:34 +0200 Subject: [Wtr-development] Fwd: Watir Advertising In-Reply-To: References: <20100824124730.4r7k61i1usosgcw4@box580.bluehost.com> Message-ID: If you search for "Ads on watir.com" on wtr-development and watir-general you will find our recent discussion. I remember that Alister really did not like the idea, nobody else had any complaints, as far as I found in my mail archive. Let me dream for a moment. What if we raised enough money to pay Charley to work part time (or even full time) on Watir? :) ?eljko -------------- next part -------------- An HTML attachment was scrubbed... URL: