From watirjira at gmail.com  Mon Jul  4 13:31:09 2011
From: watirjira at gmail.com (Michael M (JIRA))
Date: Mon, 4 Jul 2011 12:31:09 -0500 (CDT)
Subject: [Wtr-development] [JIRA] Created: (WTR-483) Watir broken -
 Watir::Browser.new fails on Windows XP with IE 8
Message-ID: <256942.34.1309800669927.JavaMail.oqa-j2ee@openqa01.managed.contegix.com>

Watir broken - Watir::Browser.new fails on Windows XP with IE 8
---------------------------------------------------------------

                 Key: WTR-483
                 URL: http://jira.openqa.org/browse/WTR-483
             Project: Watir
          Issue Type: Bug
          Components: Frame, Other, Project Support, Window Attachment
    Affects Versions: 1.8.0
         Environment: Windows XP Pro x64 SP2
            Reporter: Michael M
            Priority: Blocker
             Fix For: Soon


ruby 1.9.2p180 (2011-02-18) [i386-mingw32]
watir (1.9.1)
commonwatir (1.9.1)

A very simple script no longer runs at all, not much else to say:

require 'watir'

browser = Watir::Browser.new
browser.goto 'http://www.google.ca'

The following exception occurs:

C:/Ruby192/lib/ruby/gems/1.9.1/gems/commonwatir-1.9.1/lib/watir/browser.rb:89:in `eval': undefined method `class_eval' for [["RAutomation"]]:Array (NoMethodError)
        from C:/Ruby192/lib/ruby/gems/1.9.1/gems/rautomation-0.6.0/lib/rautomation/element_collections.rb:8:in `each'
        from C:/Ruby192/lib/ruby/gems/1.9.1/gems/rautomation-0.6.0/lib/rautomation/element_collections.rb:8:in `has_many'
        from C:/Ruby192/lib/ruby/gems/1.9.1/gems/rautomation-0.6.0/lib/rautomation/window.rb:15:in `<class:Window>'
        from C:/Ruby192/lib/ruby/gems/1.9.1/gems/rautomation-0.6.0/lib/rautomation/window.rb:11:in `<module:RAutomation>'
        from C:/Ruby192/lib/ruby/gems/1.9.1/gems/rautomation-0.6.0/lib/rautomation/window.rb:1:in `<top (required)>'
        from C:/Ruby192/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
        from C:/Ruby192/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
        from C:/Ruby192/lib/ruby/gems/1.9.1/gems/rautomation-0.6.0/lib/rautomation.rb:6:in `<top (required)>'
        from C:/Ruby192/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
        from C:/Ruby192/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
        from C:/Ruby192/lib/ruby/gems/1.9.1/gems/watir-1.9.1/lib/watir/core.rb:36:in `<top (required)>'
        from C:/Ruby192/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
        from C:/Ruby192/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
        from C:/Ruby192/lib/ruby/gems/1.9.1/gems/watir-1.9.1/lib/watir/ie.rb:2:in `<top (required)>'
        from (eval):1:in `klass'
        from C:/Ruby192/lib/ruby/gems/1.9.1/gems/commonwatir-1.9.1/lib/watir/browser.rb:89:in `eval'
        from C:/Ruby192/lib/ruby/gems/1.9.1/gems/commonwatir-1.9.1/lib/watir/browser.rb:89:in `klass'
        from C:/Ruby192/lib/ruby/gems/1.9.1/gems/commonwatir-1.9.1/lib/watir/browser.rb:79:in `set_options'
        from C:/Ruby192/lib/ruby/gems/1.9.1/gems/commonwatir-1.9.1/lib/watir/browser.rb:142:in `set_sub_options'
        from C:/Ruby192/lib/ruby/gems/1.9.1/gems/commonwatir-1.9.1/lib/watir/browser.rb:64:in `new'
        from DivsTest.rb:3:in `<main>'


-- 
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 Jul  4 13:55:10 2011
From: watirjira at gmail.com (Hugh (JIRA))
Date: Mon, 4 Jul 2011 12:55:10 -0500 (CDT)
Subject: [Wtr-development] [JIRA] Commented: (WTR-483) Watir broken -
 Watir::Browser.new fails on Windows XP with IE 8
In-Reply-To: <256942.34.1309800669927.JavaMail.oqa-j2ee@openqa01.managed.contegix.com>
Message-ID: <32311961.36.1309802110696.JavaMail.oqa-j2ee@openqa01.managed.contegix.com>


    [ http://jira.openqa.org/browse/WTR-483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20203#action_20203 ] 

Hugh commented on WTR-483:
--------------------------

I was able to reproduce this. I only see it on Ruby 1.9.2 with rautomation 0.6.0. If you revert rautomation back to 0.5.1 it should work

Note that Ruby 1.8.7 works fine with the latest watir and rautomation.  

> Watir broken - Watir::Browser.new fails on Windows XP with IE 8
> ---------------------------------------------------------------
>
>                 Key: WTR-483
>                 URL: http://jira.openqa.org/browse/WTR-483
>             Project: Watir
>          Issue Type: Bug
>          Components: Frame, Other, Project Support, Window Attachment
>    Affects Versions: 1.8.0
>         Environment: Windows XP Pro x64 SP2
>            Reporter: Michael M
>            Priority: Blocker
>             Fix For: Soon
>
>
> ruby 1.9.2p180 (2011-02-18) [i386-mingw32]
> watir (1.9.1)
> commonwatir (1.9.1)
> A very simple script no longer runs at all, not much else to say:
> require 'watir'
> browser = Watir::Browser.new
> browser.goto 'http://www.google.ca'
> The following exception occurs:
> C:/Ruby192/lib/ruby/gems/1.9.1/gems/commonwatir-1.9.1/lib/watir/browser.rb:89:in `eval': undefined method `class_eval' for [["RAutomation"]]:Array (NoMethodError)
>         from C:/Ruby192/lib/ruby/gems/1.9.1/gems/rautomation-0.6.0/lib/rautomation/element_collections.rb:8:in `each'
>         from C:/Ruby192/lib/ruby/gems/1.9.1/gems/rautomation-0.6.0/lib/rautomation/element_collections.rb:8:in `has_many'
>         from C:/Ruby192/lib/ruby/gems/1.9.1/gems/rautomation-0.6.0/lib/rautomation/window.rb:15:in `<class:Window>'
>         from C:/Ruby192/lib/ruby/gems/1.9.1/gems/rautomation-0.6.0/lib/rautomation/window.rb:11:in `<module:RAutomation>'
>         from C:/Ruby192/lib/ruby/gems/1.9.1/gems/rautomation-0.6.0/lib/rautomation/window.rb:1:in `<top (required)>'
>         from C:/Ruby192/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
>         from C:/Ruby192/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
>         from C:/Ruby192/lib/ruby/gems/1.9.1/gems/rautomation-0.6.0/lib/rautomation.rb:6:in `<top (required)>'
>         from C:/Ruby192/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
>         from C:/Ruby192/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
>         from C:/Ruby192/lib/ruby/gems/1.9.1/gems/watir-1.9.1/lib/watir/core.rb:36:in `<top (required)>'
>         from C:/Ruby192/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
>         from C:/Ruby192/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
>         from C:/Ruby192/lib/ruby/gems/1.9.1/gems/watir-1.9.1/lib/watir/ie.rb:2:in `<top (required)>'
>         from (eval):1:in `klass'
>         from C:/Ruby192/lib/ruby/gems/1.9.1/gems/commonwatir-1.9.1/lib/watir/browser.rb:89:in `eval'
>         from C:/Ruby192/lib/ruby/gems/1.9.1/gems/commonwatir-1.9.1/lib/watir/browser.rb:89:in `klass'
>         from C:/Ruby192/lib/ruby/gems/1.9.1/gems/commonwatir-1.9.1/lib/watir/browser.rb:79:in `set_options'
>         from C:/Ruby192/lib/ruby/gems/1.9.1/gems/commonwatir-1.9.1/lib/watir/browser.rb:142:in `set_sub_options'
>         from C:/Ruby192/lib/ruby/gems/1.9.1/gems/commonwatir-1.9.1/lib/watir/browser.rb:64:in `new'
>         from DivsTest.rb:3:in `<main>'

-- 
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 Jul  5 09:32:34 2011
From: watirjira at gmail.com (Jarmo Pertman (JIRA))
Date: Tue, 5 Jul 2011 08:32:34 -0500 (CDT)
Subject: [Wtr-development] [JIRA] Commented: (WTR-483) Watir broken -
 Watir::Browser.new fails on Windows XP with IE 8
In-Reply-To: <256942.34.1309800669927.JavaMail.oqa-j2ee@openqa01.managed.contegix.com>
Message-ID: <19796012.3.1309872754278.JavaMail.oqa-j2ee@openqa01.managed.contegix.com>


    [ http://jira.openqa.org/browse/WTR-483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20210#action_20210 ] 

Jarmo Pertman commented on WTR-483:
-----------------------------------

It should be okay now in RAutomation 0.6.1. Try gem install rautomation and let us know.

> Watir broken - Watir::Browser.new fails on Windows XP with IE 8
> ---------------------------------------------------------------
>
>                 Key: WTR-483
>                 URL: http://jira.openqa.org/browse/WTR-483
>             Project: Watir
>          Issue Type: Bug
>          Components: Frame, Other, Project Support, Window Attachment
>    Affects Versions: 1.8.0
>         Environment: Windows XP Pro x64 SP2
>            Reporter: Michael M
>            Priority: Blocker
>             Fix For: Soon
>
>
> ruby 1.9.2p180 (2011-02-18) [i386-mingw32]
> watir (1.9.1)
> commonwatir (1.9.1)
> A very simple script no longer runs at all, not much else to say:
> require 'watir'
> browser = Watir::Browser.new
> browser.goto 'http://www.google.ca'
> The following exception occurs:
> C:/Ruby192/lib/ruby/gems/1.9.1/gems/commonwatir-1.9.1/lib/watir/browser.rb:89:in `eval': undefined method `class_eval' for [["RAutomation"]]:Array (NoMethodError)
>         from C:/Ruby192/lib/ruby/gems/1.9.1/gems/rautomation-0.6.0/lib/rautomation/element_collections.rb:8:in `each'
>         from C:/Ruby192/lib/ruby/gems/1.9.1/gems/rautomation-0.6.0/lib/rautomation/element_collections.rb:8:in `has_many'
>         from C:/Ruby192/lib/ruby/gems/1.9.1/gems/rautomation-0.6.0/lib/rautomation/window.rb:15:in `<class:Window>'
>         from C:/Ruby192/lib/ruby/gems/1.9.1/gems/rautomation-0.6.0/lib/rautomation/window.rb:11:in `<module:RAutomation>'
>         from C:/Ruby192/lib/ruby/gems/1.9.1/gems/rautomation-0.6.0/lib/rautomation/window.rb:1:in `<top (required)>'
>         from C:/Ruby192/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
>         from C:/Ruby192/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
>         from C:/Ruby192/lib/ruby/gems/1.9.1/gems/rautomation-0.6.0/lib/rautomation.rb:6:in `<top (required)>'
>         from C:/Ruby192/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
>         from C:/Ruby192/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
>         from C:/Ruby192/lib/ruby/gems/1.9.1/gems/watir-1.9.1/lib/watir/core.rb:36:in `<top (required)>'
>         from C:/Ruby192/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
>         from C:/Ruby192/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
>         from C:/Ruby192/lib/ruby/gems/1.9.1/gems/watir-1.9.1/lib/watir/ie.rb:2:in `<top (required)>'
>         from (eval):1:in `klass'
>         from C:/Ruby192/lib/ruby/gems/1.9.1/gems/commonwatir-1.9.1/lib/watir/browser.rb:89:in `eval'
>         from C:/Ruby192/lib/ruby/gems/1.9.1/gems/commonwatir-1.9.1/lib/watir/browser.rb:89:in `klass'
>         from C:/Ruby192/lib/ruby/gems/1.9.1/gems/commonwatir-1.9.1/lib/watir/browser.rb:79:in `set_options'
>         from C:/Ruby192/lib/ruby/gems/1.9.1/gems/commonwatir-1.9.1/lib/watir/browser.rb:142:in `set_sub_options'
>         from C:/Ruby192/lib/ruby/gems/1.9.1/gems/commonwatir-1.9.1/lib/watir/browser.rb:64:in `new'
>         from DivsTest.rb:3:in `<main>'

-- 
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  Wed Jul  6 02:15:37 2011
From: watirjira at gmail.com (Zhimin Zhan (JIRA))
Date: Wed, 6 Jul 2011 01:15:37 -0500 (CDT)
Subject: [Wtr-development] [JIRA] Created: (WTR-484) Could not open library
 RAutomation's UiaDll.dll': A dynamic link library (DLL) initialization
 routine failed.
Message-ID: <10616446.7.1309932937639.JavaMail.oqa-j2ee@openqa01.managed.contegix.com>

Could not open library RAutomation's UiaDll.dll': A dynamic link library (DLL) initialization routine failed.
-------------------------------------------------------------------------------------------------------------

                 Key: WTR-484
                 URL: http://jira.openqa.org/browse/WTR-484
             Project: Watir
          Issue Type: Bug
          Components: Other
    Affects Versions: Soon
         Environment: Windows XP
            Reporter: Zhimin Zhan
            Priority: Major


I am runing a set of tests, only first one failed due to 

ruby/gems/1.8/gems/rautomation-0.6.1/lib/rautomation/adapter/win_ffi/ms_uia/../../../../../ext/UiaDll/Release/UiaDll.dll': A dynamic link library (DLL) initialization routine failed

-- 
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  Wed Jul  6 02:17:36 2011
From: watirjira at gmail.com (Zhimin Zhan (JIRA))
Date: Wed, 6 Jul 2011 01:17:36 -0500 (CDT)
Subject: [Wtr-development] [JIRA] Commented: (WTR-484) Could not open
 library RAutomation's UiaDll.dll': A dynamic link library (DLL)
 initialization routine failed.
In-Reply-To: <10616446.7.1309932937639.JavaMail.oqa-j2ee@openqa01.managed.contegix.com>
Message-ID: <546157.9.1309933056079.JavaMail.oqa-j2ee@openqa01.managed.contegix.com>


    [ http://jira.openqa.org/browse/WTR-484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20211#action_20211 ] 

Zhimin Zhan commented on WTR-484:
---------------------------------

Sorry, forgot to mention the Watir version: 1.9.1, and Ruby 1.8.7p334 mingw32

> Could not open library RAutomation's UiaDll.dll': A dynamic link library (DLL) initialization routine failed.
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: WTR-484
>                 URL: http://jira.openqa.org/browse/WTR-484
>             Project: Watir
>          Issue Type: Bug
>          Components: Other
>    Affects Versions: Soon
>         Environment: Windows XP
>            Reporter: Zhimin Zhan
>            Priority: Major
>
> I am runing a set of tests, only first one failed due to 
> ruby/gems/1.8/gems/rautomation-0.6.1/lib/rautomation/adapter/win_ffi/ms_uia/../../../../../ext/UiaDll/Release/UiaDll.dll': A dynamic link library (DLL) initialization routine failed

-- 
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  Wed Jul  6 04:51:37 2011
From: watirjira at gmail.com (Jarmo Pertman (JIRA))
Date: Wed, 6 Jul 2011 03:51:37 -0500 (CDT)
Subject: [Wtr-development] [JIRA] Commented: (WTR-484) Could not open
 library RAutomation's UiaDll.dll': A dynamic link library (DLL)
 initialization routine failed.
In-Reply-To: <10616446.7.1309932937639.JavaMail.oqa-j2ee@openqa01.managed.contegix.com>
Message-ID: <29450918.12.1309942297324.JavaMail.oqa-j2ee@openqa01.managed.contegix.com>


    [ http://jira.openqa.org/browse/WTR-484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20212#action_20212 ] 

Jarmo Pertman commented on WTR-484:
-----------------------------------

Looking into it.

Quick & dirty fix would be to replace the file ruby/gems/1.8/gems/rautomation-0.6.1/lib/rautomation/adapter/win_ffi/ms_uia/uia_dll.rb with contents:
module RAutomation
  module Adapter
    module WinFfi
      # @private
      module UiaDll
      end
    end
  end
end

> Could not open library RAutomation's UiaDll.dll': A dynamic link library (DLL) initialization routine failed.
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: WTR-484
>                 URL: http://jira.openqa.org/browse/WTR-484
>             Project: Watir
>          Issue Type: Bug
>          Components: Other
>    Affects Versions: Soon
>         Environment: Windows XP
>            Reporter: Zhimin Zhan
>            Priority: Major
>
> I am runing a set of tests, only first one failed due to 
> ruby/gems/1.8/gems/rautomation-0.6.1/lib/rautomation/adapter/win_ffi/ms_uia/../../../../../ext/UiaDll/Release/UiaDll.dll': A dynamic link library (DLL) initialization routine failed

-- 
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  Wed Jul  6 05:30:34 2011
From: watirjira at gmail.com (Zhimin Zhan (JIRA))
Date: Wed, 6 Jul 2011 04:30:34 -0500 (CDT)
Subject: [Wtr-development] [JIRA] Commented: (WTR-484) Could not open
 library RAutomation's UiaDll.dll': A dynamic link library (DLL)
 initialization routine failed.
In-Reply-To: <10616446.7.1309932937639.JavaMail.oqa-j2ee@openqa01.managed.contegix.com>
Message-ID: <11795895.14.1309944634987.JavaMail.oqa-j2ee@openqa01.managed.contegix.com>


    [ http://jira.openqa.org/browse/WTR-484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20213#action_20213 ] 

Zhimin Zhan commented on WTR-484:
---------------------------------

Jarmo,

Thanks for such quick response.

Yes, it seems soloved the problem.

Regards,
Zhimin

> Could not open library RAutomation's UiaDll.dll': A dynamic link library (DLL) initialization routine failed.
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: WTR-484
>                 URL: http://jira.openqa.org/browse/WTR-484
>             Project: Watir
>          Issue Type: Bug
>          Components: Other
>    Affects Versions: Soon
>         Environment: Windows XP
>            Reporter: Zhimin Zhan
>            Priority: Major
>
> I am runing a set of tests, only first one failed due to 
> ruby/gems/1.8/gems/rautomation-0.6.1/lib/rautomation/adapter/win_ffi/ms_uia/../../../../../ext/UiaDll/Release/UiaDll.dll': A dynamic link library (DLL) initialization routine failed

-- 
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  Wed Jul  6 13:00:34 2011
From: watirjira at gmail.com (Michael M (JIRA))
Date: Wed, 6 Jul 2011 12:00:34 -0500 (CDT)
Subject: [Wtr-development] [JIRA] Commented: (WTR-483) Watir broken -
 Watir::Browser.new fails on Windows XP with IE 8
In-Reply-To: <256942.34.1309800669927.JavaMail.oqa-j2ee@openqa01.managed.contegix.com>
Message-ID: <10202289.17.1309971634888.JavaMail.oqa-j2ee@openqa01.managed.contegix.com>


    [ http://jira.openqa.org/browse/WTR-483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20214#action_20214 ] 

Michael M commented on WTR-483:
-------------------------------

That seems to have partially fixed the issue launching IE, but it doesn't get any further:


UiaDll: CoCreateInstance failed. hr = 0x80040154C:/Ruby192/lib/ruby/gems/1.9.1/gems/ffi-1.0.9-x86-mingw32/lib/ffi/library.rb:75:in `block in ffi_lib': Could not open library 'C:/Ruby192/lib/ruby/gems/1.9.1/gems/rautomation-0.6.1/lib/rautomation/adapter/win_ffi/ms_uia/../../../../../ext/UiaDll/Release/UiaDll.dll': A dynamic link library (DLL) init (LoadError)outine failed.
        from C:/Ruby192/lib/ruby/gems/1.9.1/gems/ffi-1.0.9-x86-mingw32/lib/ffi/library.rb:54:in `map'
        from C:/Ruby192/lib/ruby/gems/1.9.1/gems/ffi-1.0.9-x86-mingw32/lib/ffi/library.rb:54:in `ffi_lib'
        from C:/Ruby192/lib/ruby/gems/1.9.1/gems/rautomation-0.6.1/lib/rautomation/adapter/win_ffi/ms_uia/uia_dll.rb:8:in `<module:UiaDll>'
        from C:/Ruby192/lib/ruby/gems/1.9.1/gems/rautomation-0.6.1/lib/rautomation/adapter/win_ffi/ms_uia/uia_dll.rb:5:in `<module:WinFfi>'
        from C:/Ruby192/lib/ruby/gems/1.9.1/gems/rautomation-0.6.1/lib/rautomation/adapter/win_ffi/ms_uia/uia_dll.rb:3:in `<module:Adapter>'
        from C:/Ruby192/lib/ruby/gems/1.9.1/gems/rautomation-0.6.1/lib/rautomation/adapter/win_ffi/ms_uia/uia_dll.rb:2:in `<module:RAutomation>'
        from C:/Ruby192/lib/ruby/gems/1.9.1/gems/rautomation-0.6.1/lib/rautomation/adapter/win_ffi/ms_uia/uia_dll.rb:1:in `<top (required)>'
        from <internal:lib/rubygems/custom_require>:29:in `require'
        from <internal:lib/rubygems/custom_require>:29:in `require'
        from C:/Ruby192/lib/ruby/gems/1.9.1/gems/rautomation-0.6.1/lib/rautomation/adapter/win_ffi.rb:22:in `<top (required)>'
        from C:/Ruby192/lib/ruby/gems/1.9.1/gems/rautomation-0.6.1/lib/rautomation/window.rb:66:in `const_get'
        from C:/Ruby192/lib/ruby/gems/1.9.1/gems/rautomation-0.6.1/lib/rautomation/window.rb:66:in `initialize'
        from C:/Ruby192/lib/ruby/gems/1.9.1/gems/watir-1.9.1/lib/watir/ie-class.rb:459:in `new'
        from C:/Ruby192/lib/ruby/gems/1.9.1/gems/watir-1.9.1/lib/watir/ie-class.rb:459:in `rautomation'
        from C:/Ruby192/lib/ruby/gems/1.9.1/gems/watir-1.9.1/lib/watir/ie-class.rb:449:in `activate'


> Watir broken - Watir::Browser.new fails on Windows XP with IE 8
> ---------------------------------------------------------------
>
>                 Key: WTR-483
>                 URL: http://jira.openqa.org/browse/WTR-483
>             Project: Watir
>          Issue Type: Bug
>          Components: Frame, Other, Project Support, Window Attachment
>    Affects Versions: 1.8.0
>         Environment: Windows XP Pro x64 SP2
>            Reporter: Michael M
>            Priority: Blocker
>             Fix For: Soon
>
>
> ruby 1.9.2p180 (2011-02-18) [i386-mingw32]
> watir (1.9.1)
> commonwatir (1.9.1)
> A very simple script no longer runs at all, not much else to say:
> require 'watir'
> browser = Watir::Browser.new
> browser.goto 'http://www.google.ca'
> The following exception occurs:
> C:/Ruby192/lib/ruby/gems/1.9.1/gems/commonwatir-1.9.1/lib/watir/browser.rb:89:in `eval': undefined method `class_eval' for [["RAutomation"]]:Array (NoMethodError)
>         from C:/Ruby192/lib/ruby/gems/1.9.1/gems/rautomation-0.6.0/lib/rautomation/element_collections.rb:8:in `each'
>         from C:/Ruby192/lib/ruby/gems/1.9.1/gems/rautomation-0.6.0/lib/rautomation/element_collections.rb:8:in `has_many'
>         from C:/Ruby192/lib/ruby/gems/1.9.1/gems/rautomation-0.6.0/lib/rautomation/window.rb:15:in `<class:Window>'
>         from C:/Ruby192/lib/ruby/gems/1.9.1/gems/rautomation-0.6.0/lib/rautomation/window.rb:11:in `<module:RAutomation>'
>         from C:/Ruby192/lib/ruby/gems/1.9.1/gems/rautomation-0.6.0/lib/rautomation/window.rb:1:in `<top (required)>'
>         from C:/Ruby192/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
>         from C:/Ruby192/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
>         from C:/Ruby192/lib/ruby/gems/1.9.1/gems/rautomation-0.6.0/lib/rautomation.rb:6:in `<top (required)>'
>         from C:/Ruby192/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
>         from C:/Ruby192/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
>         from C:/Ruby192/lib/ruby/gems/1.9.1/gems/watir-1.9.1/lib/watir/core.rb:36:in `<top (required)>'
>         from C:/Ruby192/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
>         from C:/Ruby192/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
>         from C:/Ruby192/lib/ruby/gems/1.9.1/gems/watir-1.9.1/lib/watir/ie.rb:2:in `<top (required)>'
>         from (eval):1:in `klass'
>         from C:/Ruby192/lib/ruby/gems/1.9.1/gems/commonwatir-1.9.1/lib/watir/browser.rb:89:in `eval'
>         from C:/Ruby192/lib/ruby/gems/1.9.1/gems/commonwatir-1.9.1/lib/watir/browser.rb:89:in `klass'
>         from C:/Ruby192/lib/ruby/gems/1.9.1/gems/commonwatir-1.9.1/lib/watir/browser.rb:79:in `set_options'
>         from C:/Ruby192/lib/ruby/gems/1.9.1/gems/commonwatir-1.9.1/lib/watir/browser.rb:142:in `set_sub_options'
>         from C:/Ruby192/lib/ruby/gems/1.9.1/gems/commonwatir-1.9.1/lib/watir/browser.rb:64:in `new'
>         from DivsTest.rb:3:in `<main>'

-- 
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 Jul  7 05:45:59 2011
From: watirjira at gmail.com (Jarmo Pertman (JIRA))
Date: Thu, 7 Jul 2011 04:45:59 -0500 (CDT)
Subject: [Wtr-development] [JIRA] Commented: (WTR-484) Could not open
 library RAutomation's UiaDll.dll': A dynamic link library (DLL)
 initialization routine failed.
In-Reply-To: <10616446.7.1309932937639.JavaMail.oqa-j2ee@openqa01.managed.contegix.com>
Message-ID: <28646007.2.1310031959433.JavaMail.oqa-j2ee@openqa01.managed.contegix.com>


    [ http://jira.openqa.org/browse/WTR-484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20220#action_20220 ] 

Jarmo Pertman commented on WTR-484:
-----------------------------------

It seems that the problem is with Windows XP. I managed to reproduce it on my VM. If anyone is having the problem under non-XP, then please let us know about it.

> Could not open library RAutomation's UiaDll.dll': A dynamic link library (DLL) initialization routine failed.
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: WTR-484
>                 URL: http://jira.openqa.org/browse/WTR-484
>             Project: Watir
>          Issue Type: Bug
>          Components: Other
>    Affects Versions: Soon
>         Environment: Windows XP
>            Reporter: Zhimin Zhan
>            Priority: Major
>
> I am runing a set of tests, only first one failed due to 
> ruby/gems/1.8/gems/rautomation-0.6.1/lib/rautomation/adapter/win_ffi/ms_uia/../../../../../ext/UiaDll/Release/UiaDll.dll': A dynamic link library (DLL) initialization routine failed

-- 
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 Jul  7 09:52:59 2011
From: watirjira at gmail.com (Stephan Schwab (JIRA))
Date: Thu, 7 Jul 2011 08:52:59 -0500 (CDT)
Subject: [Wtr-development] [JIRA] Commented: (WTR-484) Could not open
 library RAutomation's UiaDll.dll': A dynamic link library (DLL)
 initialization routine failed.
In-Reply-To: <10616446.7.1309932937639.JavaMail.oqa-j2ee@openqa01.managed.contegix.com>
Message-ID: <9081038.6.1310046779536.JavaMail.oqa-j2ee@openqa01.managed.contegix.com>


    [ http://jira.openqa.org/browse/WTR-484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20221#action_20221 ] 

Stephan Schwab commented on WTR-484:
------------------------------------

There is a platform update for Windows XP. It appears that most users of XP have this installed. This seems to be the way to run current software on the now - as far as I know - unsupported Windows XP.

A plain XP system on SR2 level will not have UIAutomation and probably neither MS Active Accessibility.

> Could not open library RAutomation's UiaDll.dll': A dynamic link library (DLL) initialization routine failed.
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: WTR-484
>                 URL: http://jira.openqa.org/browse/WTR-484
>             Project: Watir
>          Issue Type: Bug
>          Components: Other
>    Affects Versions: Soon
>         Environment: Windows XP
>            Reporter: Zhimin Zhan
>            Priority: Major
>
> I am runing a set of tests, only first one failed due to 
> ruby/gems/1.8/gems/rautomation-0.6.1/lib/rautomation/adapter/win_ffi/ms_uia/../../../../../ext/UiaDll/Release/UiaDll.dll': A dynamic link library (DLL) initialization routine failed

-- 
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 jarmo.p at gmail.com  Thu Jul  7 11:17:34 2011
From: jarmo.p at gmail.com (Jarmo)
Date: Thu, 7 Jul 2011 18:17:34 +0300
Subject: [Wtr-development] suggestion: do not raise UnknownObjectException
	with #exists?
Message-ID: <CAHZHd6WqoqDFMtzV-FXjz1JUY7q1zxzY1FP8AScO4FXv7GqQyA@mail.gmail.com>

Hi!

Currently if there's some elements which doesn't exist, but will exist
after some time (for example, after some ajax request), then i have to
do something like this:
browser.wait_until {div(:id => 'doesntexist').span(:class =>
'doesntexisteither').exists? rescue false}
or
browser.wait_until {div(:id => 'doesntexist').exists? && div(:id =>
'doesntexist).span(:class => 'doesntexisteither')}

I don't like much both of the ways and started thinking that what if
#exists? returned a boolean all the time? What if it returns false if
the parent element doesn't exist instead of raising that unneeded
exception? Since this would be a core change, i'd like to know what do
you think and/or how do you handle situations like these in your
tests?

How does watir-webdriver handle these situations?

Jarmo

From bret at pettichord.com  Thu Jul  7 12:13:56 2011
From: bret at pettichord.com (Bret Pettichord)
Date: Thu, 7 Jul 2011 11:13:56 -0500
Subject: [Wtr-development] suggestion: do not raise
 UnknownObjectException with #exists?
In-Reply-To: <CAHZHd6WqoqDFMtzV-FXjz1JUY7q1zxzY1FP8AScO4FXv7GqQyA@mail.gmail.com>
References: <CAHZHd6WqoqDFMtzV-FXjz1JUY7q1zxzY1FP8AScO4FXv7GqQyA@mail.gmail.com>
Message-ID: <CAPjkWY3tKovuUepmMYs_yrziX2bm9a-ygO8yGac5mYBrs=MTUQ@mail.gmail.com>

I think I tried to do this years ago, but found it to be too difficult. How
would you do it?

Bret

On Thu, Jul 7, 2011 at 10:17 AM, Jarmo <jarmo.p at gmail.com> wrote:

> Hi!
>
> Currently if there's some elements which doesn't exist, but will exist
> after some time (for example, after some ajax request), then i have to
> do something like this:
> browser.wait_until {div(:id => 'doesntexist').span(:class =>
> 'doesntexisteither').exists? rescue false}
> or
> browser.wait_until {div(:id => 'doesntexist').exists? && div(:id =>
> 'doesntexist).span(:class => 'doesntexisteither')}
>
> I don't like much both of the ways and started thinking that what if
> #exists? returned a boolean all the time? What if it returns false if
> the parent element doesn't exist instead of raising that unneeded
> exception? Since this would be a core change, i'd like to know what do
> you think and/or how do you handle situations like these in your
> tests?
>
> How does watir-webdriver handle these situations?
>
> Jarmo
> _______________________________________________
> Wtr-development mailing list
> Wtr-development at rubyforge.org
> http://rubyforge.org/mailman/listinfo/wtr-development
>



-- 
Bret Pettichord
Director, Watir Project, www.watir.com

Blog, www.testingwithvision.com
Twitter, www.twitter.com/bpettichord
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/wtr-development/attachments/20110707/76b529b3/attachment-0001.html>

From watirjira at gmail.com  Thu Jul  7 12:14:59 2011
From: watirjira at gmail.com (Jarmo Pertman (JIRA))
Date: Thu, 7 Jul 2011 11:14:59 -0500 (CDT)
Subject: [Wtr-development] [JIRA] Closed: (WTR-484) Could not open library
 RAutomation's UiaDll.dll': A dynamic link library (DLL) initialization
 routine failed.
In-Reply-To: <10616446.7.1309932937639.JavaMail.oqa-j2ee@openqa01.managed.contegix.com>
Message-ID: <7436434.8.1310055299023.JavaMail.oqa-j2ee@openqa01.managed.contegix.com>


     [ http://jira.openqa.org/browse/WTR-484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jarmo Pertman closed WTR-484.
-----------------------------

       Resolution: Fixed
    Fix Version/s: Soon

Stephan, thank you for the insights!

I've made to load UiaDll now by autoload (e.g. lazily), which means that everything should be working again for Watir users since it doesn't use RAutomation's functionality with UiaDll at all:
https://github.com/jarmo/RAutomation/commit/ed2a6f5330abd2f45e191c47b7ad927e5580a7de

Stephan, do you know exactly what update should be installed so i could make some specific note about it in RAutomation's readme, comments or wiki if someone really needs to use the above mentioned functionality?

Closing this bug for now.

> Could not open library RAutomation's UiaDll.dll': A dynamic link library (DLL) initialization routine failed.
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: WTR-484
>                 URL: http://jira.openqa.org/browse/WTR-484
>             Project: Watir
>          Issue Type: Bug
>          Components: Other
>    Affects Versions: Soon
>         Environment: Windows XP
>            Reporter: Zhimin Zhan
>            Priority: Major
>             Fix For: Soon
>
>
> I am runing a set of tests, only first one failed due to 
> ruby/gems/1.8/gems/rautomation-0.6.1/lib/rautomation/adapter/win_ffi/ms_uia/../../../../../ext/UiaDll/Release/UiaDll.dll': A dynamic link library (DLL) initialization routine failed

-- 
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 jarmo.p at gmail.com  Thu Jul  7 12:16:33 2011
From: jarmo.p at gmail.com (Jarmo)
Date: Thu, 7 Jul 2011 19:16:33 +0300
Subject: [Wtr-development] suggestion: do not raise
 UnknownObjectException with #exists?
In-Reply-To: <CAPjkWY3tKovuUepmMYs_yrziX2bm9a-ygO8yGac5mYBrs=MTUQ@mail.gmail.com>
References: <CAHZHd6WqoqDFMtzV-FXjz1JUY7q1zxzY1FP8AScO4FXv7GqQyA@mail.gmail.com>
	<CAPjkWY3tKovuUepmMYs_yrziX2bm9a-ygO8yGac5mYBrs=MTUQ@mail.gmail.com>
Message-ID: <CAHZHd6VvAF5zk-GfdubiU3c2=cCSj=7xDBcgEsWk0y9hF0+-ww@mail.gmail.com>

Haven't digged into technicalities yet. Just wanted to make sure that
this behavior would make sense to everyone else too before starting to
spend time on it.

Jarmo

On Thu, Jul 7, 2011 at 7:13 PM, Bret Pettichord <bret at pettichord.com> wrote:
> I think I tried to do this years ago, but found it to be too difficult. How
> would you do it?
>
> Bret
>
> On Thu, Jul 7, 2011 at 10:17 AM, Jarmo <jarmo.p at gmail.com> wrote:
>>
>> Hi!
>>
>> Currently if there's some elements which doesn't exist, but will exist
>> after some time (for example, after some ajax request), then i have to
>> do something like this:
>> browser.wait_until {div(:id => 'doesntexist').span(:class =>
>> 'doesntexisteither').exists? rescue false}
>> or
>> browser.wait_until {div(:id => 'doesntexist').exists? && div(:id =>
>> 'doesntexist).span(:class => 'doesntexisteither')}
>>
>> I don't like much both of the ways and started thinking that what if
>> #exists? returned a boolean all the time? What if it returns false if
>> the parent element doesn't exist instead of raising that unneeded
>> exception? Since this would be a core change, i'd like to know what do
>> you think and/or how do you handle situations like these in your
>> tests?
>>
>> How does watir-webdriver handle these situations?
>>
>> Jarmo
>> _______________________________________________
>> Wtr-development mailing list
>> Wtr-development at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/wtr-development
>
>
>
> --
> Bret Pettichord
> Director, Watir Project, www.watir.com
>
> Blog, www.testingwithvision.com
> Twitter, www.twitter.com/bpettichord
>
>
> _______________________________________________
> Wtr-development mailing list
> Wtr-development at rubyforge.org
> http://rubyforge.org/mailman/listinfo/wtr-development
>

From watirjira at gmail.com  Thu Jul  7 12:18:58 2011
From: watirjira at gmail.com (Jarmo Pertman (JIRA))
Date: Thu, 7 Jul 2011 11:18:58 -0500 (CDT)
Subject: [Wtr-development] [JIRA] Commented: (WTR-484) Could not open
 library RAutomation's UiaDll.dll': A dynamic link library (DLL)
 initialization routine failed.
In-Reply-To: <10616446.7.1309932937639.JavaMail.oqa-j2ee@openqa01.managed.contegix.com>
Message-ID: <3764883.10.1310055538872.JavaMail.oqa-j2ee@openqa01.managed.contegix.com>


    [ http://jira.openqa.org/browse/WTR-484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20223#action_20223 ] 

Jarmo Pertman commented on WTR-484:
-----------------------------------

Forgot to mention that "gem install rautomation" to get version 0.6.2 or newer should fix the problem.

> Could not open library RAutomation's UiaDll.dll': A dynamic link library (DLL) initialization routine failed.
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: WTR-484
>                 URL: http://jira.openqa.org/browse/WTR-484
>             Project: Watir
>          Issue Type: Bug
>          Components: Other
>    Affects Versions: Soon
>         Environment: Windows XP
>            Reporter: Zhimin Zhan
>            Priority: Major
>             Fix For: Soon
>
>
> I am runing a set of tests, only first one failed due to 
> ruby/gems/1.8/gems/rautomation-0.6.1/lib/rautomation/adapter/win_ffi/ms_uia/../../../../../ext/UiaDll/Release/UiaDll.dll': A dynamic link library (DLL) initialization routine failed

-- 
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 Jul  7 12:24:58 2011
From: watirjira at gmail.com (Jarmo Pertman (JIRA))
Date: Thu, 7 Jul 2011 11:24:58 -0500 (CDT)
Subject: [Wtr-development] [JIRA] Commented: (WTR-483) Watir broken -
 Watir::Browser.new fails on Windows XP with IE 8
In-Reply-To: <256942.34.1309800669927.JavaMail.oqa-j2ee@openqa01.managed.contegix.com>
Message-ID: <24248090.12.1310055898688.JavaMail.oqa-j2ee@openqa01.managed.contegix.com>


    [ http://jira.openqa.org/browse/WTR-483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20224#action_20224 ] 

Jarmo Pertman commented on WTR-483:
-----------------------------------

This problem is related with another bug only happening on Windows XP - http://jira.openqa.org/browse/WTR-484

gem install rautomation to install 0.6.2 or newer should fix that too.

> Watir broken - Watir::Browser.new fails on Windows XP with IE 8
> ---------------------------------------------------------------
>
>                 Key: WTR-483
>                 URL: http://jira.openqa.org/browse/WTR-483
>             Project: Watir
>          Issue Type: Bug
>          Components: Frame, Other, Project Support, Window Attachment
>    Affects Versions: 1.8.0
>         Environment: Windows XP Pro x64 SP2
>            Reporter: Michael M
>            Priority: Blocker
>             Fix For: Soon
>
>
> ruby 1.9.2p180 (2011-02-18) [i386-mingw32]
> watir (1.9.1)
> commonwatir (1.9.1)
> A very simple script no longer runs at all, not much else to say:
> require 'watir'
> browser = Watir::Browser.new
> browser.goto 'http://www.google.ca'
> The following exception occurs:
> C:/Ruby192/lib/ruby/gems/1.9.1/gems/commonwatir-1.9.1/lib/watir/browser.rb:89:in `eval': undefined method `class_eval' for [["RAutomation"]]:Array (NoMethodError)
>         from C:/Ruby192/lib/ruby/gems/1.9.1/gems/rautomation-0.6.0/lib/rautomation/element_collections.rb:8:in `each'
>         from C:/Ruby192/lib/ruby/gems/1.9.1/gems/rautomation-0.6.0/lib/rautomation/element_collections.rb:8:in `has_many'
>         from C:/Ruby192/lib/ruby/gems/1.9.1/gems/rautomation-0.6.0/lib/rautomation/window.rb:15:in `<class:Window>'
>         from C:/Ruby192/lib/ruby/gems/1.9.1/gems/rautomation-0.6.0/lib/rautomation/window.rb:11:in `<module:RAutomation>'
>         from C:/Ruby192/lib/ruby/gems/1.9.1/gems/rautomation-0.6.0/lib/rautomation/window.rb:1:in `<top (required)>'
>         from C:/Ruby192/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
>         from C:/Ruby192/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
>         from C:/Ruby192/lib/ruby/gems/1.9.1/gems/rautomation-0.6.0/lib/rautomation.rb:6:in `<top (required)>'
>         from C:/Ruby192/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
>         from C:/Ruby192/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
>         from C:/Ruby192/lib/ruby/gems/1.9.1/gems/watir-1.9.1/lib/watir/core.rb:36:in `<top (required)>'
>         from C:/Ruby192/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
>         from C:/Ruby192/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
>         from C:/Ruby192/lib/ruby/gems/1.9.1/gems/watir-1.9.1/lib/watir/ie.rb:2:in `<top (required)>'
>         from (eval):1:in `klass'
>         from C:/Ruby192/lib/ruby/gems/1.9.1/gems/commonwatir-1.9.1/lib/watir/browser.rb:89:in `eval'
>         from C:/Ruby192/lib/ruby/gems/1.9.1/gems/commonwatir-1.9.1/lib/watir/browser.rb:89:in `klass'
>         from C:/Ruby192/lib/ruby/gems/1.9.1/gems/commonwatir-1.9.1/lib/watir/browser.rb:79:in `set_options'
>         from C:/Ruby192/lib/ruby/gems/1.9.1/gems/commonwatir-1.9.1/lib/watir/browser.rb:142:in `set_sub_options'
>         from C:/Ruby192/lib/ruby/gems/1.9.1/gems/commonwatir-1.9.1/lib/watir/browser.rb:64:in `new'
>         from DivsTest.rb:3:in `<main>'

-- 
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  Thu Jul  7 12:27:36 2011
From: charley.baker at gmail.com (Charley Baker)
Date: Thu, 7 Jul 2011 10:27:36 -0600
Subject: [Wtr-development] suggestion: do not raise
 UnknownObjectException with #exists?
In-Reply-To: <CAHZHd6VvAF5zk-GfdubiU3c2=cCSj=7xDBcgEsWk0y9hF0+-ww@mail.gmail.com>
References: <CAHZHd6WqoqDFMtzV-FXjz1JUY7q1zxzY1FP8AScO4FXv7GqQyA@mail.gmail.com>
	<CAPjkWY3tKovuUepmMYs_yrziX2bm9a-ygO8yGac5mYBrs=MTUQ@mail.gmail.com>
	<CAHZHd6VvAF5zk-GfdubiU3c2=cCSj=7xDBcgEsWk0y9hF0+-ww@mail.gmail.com>
Message-ID: <CAOX+1PcbFRF7X-JK8B4Q1X1w976_br8pG4DPPb107XHf69Qkww@mail.gmail.com>

I also think it's a great idea. I remember talking about it with Bret at one
point, and it was more challenging than it seemed at first glance. I've also
had to do the wait_until blocks with rescue for Ajaxy pages. exists? should
not explode imho.

Cheers,

Charley



On Thu, Jul 7, 2011 at 10:16 AM, Jarmo <jarmo.p at gmail.com> wrote:

> Haven't digged into technicalities yet. Just wanted to make sure that
> this behavior would make sense to everyone else too before starting to
> spend time on it.
>
> Jarmo
>
> On Thu, Jul 7, 2011 at 7:13 PM, Bret Pettichord <bret at pettichord.com>
> wrote:
> > I think I tried to do this years ago, but found it to be too difficult.
> How
> > would you do it?
> >
> > Bret
> >
> > On Thu, Jul 7, 2011 at 10:17 AM, Jarmo <jarmo.p at gmail.com> wrote:
> >>
> >> Hi!
> >>
> >> Currently if there's some elements which doesn't exist, but will exist
> >> after some time (for example, after some ajax request), then i have to
> >> do something like this:
> >> browser.wait_until {div(:id => 'doesntexist').span(:class =>
> >> 'doesntexisteither').exists? rescue false}
> >> or
> >> browser.wait_until {div(:id => 'doesntexist').exists? && div(:id =>
> >> 'doesntexist).span(:class => 'doesntexisteither')}
> >>
> >> I don't like much both of the ways and started thinking that what if
> >> #exists? returned a boolean all the time? What if it returns false if
> >> the parent element doesn't exist instead of raising that unneeded
> >> exception? Since this would be a core change, i'd like to know what do
> >> you think and/or how do you handle situations like these in your
> >> tests?
> >>
> >> How does watir-webdriver handle these situations?
> >>
> >> Jarmo
> >> _______________________________________________
> >> Wtr-development mailing list
> >> Wtr-development at rubyforge.org
> >> http://rubyforge.org/mailman/listinfo/wtr-development
> >
> >
> >
> > --
> > Bret Pettichord
> > Director, Watir Project, www.watir.com
> >
> > Blog, www.testingwithvision.com
> > Twitter, www.twitter.com/bpettichord
> >
> >
> > _______________________________________________
> > 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: <http://rubyforge.org/pipermail/wtr-development/attachments/20110707/8b6bcc82/attachment.html>

From jarmo.p at gmail.com  Thu Jul  7 13:31:15 2011
From: jarmo.p at gmail.com (Jarmo)
Date: Thu, 7 Jul 2011 20:31:15 +0300
Subject: [Wtr-development] suggestion: do not raise
 UnknownObjectException with #exists?
In-Reply-To: <CAOX+1PcbFRF7X-JK8B4Q1X1w976_br8pG4DPPb107XHf69Qkww@mail.gmail.com>
References: <CAHZHd6WqoqDFMtzV-FXjz1JUY7q1zxzY1FP8AScO4FXv7GqQyA@mail.gmail.com>
	<CAPjkWY3tKovuUepmMYs_yrziX2bm9a-ygO8yGac5mYBrs=MTUQ@mail.gmail.com>
	<CAHZHd6VvAF5zk-GfdubiU3c2=cCSj=7xDBcgEsWk0y9hF0+-ww@mail.gmail.com>
	<CAOX+1PcbFRF7X-JK8B4Q1X1w976_br8pG4DPPb107XHf69Qkww@mail.gmail.com>
Message-ID: <CAHZHd6XRs=FyxPHYdF_PZxXPSUZRnYzyKAr5gCv1eKsw2T76bQ@mail.gmail.com>

Thanks for the challenge :P
https://github.com/bret/watir/commit/4393747a6fb1ce698aa9c89fb36965985e8ddd28

I'd like to make a new release soon with the following changes:
* Bump RAutomation dependency version to 0.6.2 to:
 - fix/improve Watir::IE#send_keys.
 - fix Watir::IE loading for certain Windows XP environments
(http://jira.openqa.org/browse/WTR-484).
* Restored Watir::IE#autoit method to use RAutomation's AutoIt adapter
with a deprecation warning.
* Cache IE.version result to not access registry with each execution -
was causing slowness in TextField#set for example.
* Do not raise UnknownObjectException if parent element doesn't exist
when calling Element#exists?

Any objections?

Jarmo

On Thu, Jul 7, 2011 at 7:27 PM, Charley Baker <charley.baker at gmail.com> wrote:
> I also think it's a great idea. I remember talking about it with Bret at one
> point, and it was more challenging than it seemed at first glance. I've also
> had to do the wait_until blocks with rescue for Ajaxy pages. exists? should
> not explode imho.
> Cheers,
> Charley
>
>
> On Thu, Jul 7, 2011 at 10:16 AM, Jarmo <jarmo.p at gmail.com> wrote:
>>
>> Haven't digged into technicalities yet. Just wanted to make sure that
>> this behavior would make sense to everyone else too before starting to
>> spend time on it.
>>
>> Jarmo
>>
>> On Thu, Jul 7, 2011 at 7:13 PM, Bret Pettichord <bret at pettichord.com>
>> wrote:
>> > I think I tried to do this years ago, but found it to be too difficult.
>> > How
>> > would you do it?
>> >
>> > Bret
>> >
>> > On Thu, Jul 7, 2011 at 10:17 AM, Jarmo <jarmo.p at gmail.com> wrote:
>> >>
>> >> Hi!
>> >>
>> >> Currently if there's some elements which doesn't exist, but will exist
>> >> after some time (for example, after some ajax request), then i have to
>> >> do something like this:
>> >> browser.wait_until {div(:id => 'doesntexist').span(:class =>
>> >> 'doesntexisteither').exists? rescue false}
>> >> or
>> >> browser.wait_until {div(:id => 'doesntexist').exists? && div(:id =>
>> >> 'doesntexist).span(:class => 'doesntexisteither')}
>> >>
>> >> I don't like much both of the ways and started thinking that what if
>> >> #exists? returned a boolean all the time? What if it returns false if
>> >> the parent element doesn't exist instead of raising that unneeded
>> >> exception? Since this would be a core change, i'd like to know what do
>> >> you think and/or how do you handle situations like these in your
>> >> tests?
>> >>
>> >> How does watir-webdriver handle these situations?
>> >>
>> >> Jarmo
>> >> _______________________________________________
>> >> Wtr-development mailing list
>> >> Wtr-development at rubyforge.org
>> >> http://rubyforge.org/mailman/listinfo/wtr-development
>> >
>> >
>> >
>> > --
>> > Bret Pettichord
>> > Director, Watir Project, www.watir.com
>> >
>> > Blog, www.testingwithvision.com
>> > Twitter, www.twitter.com/bpettichord
>> >
>> >
>> > _______________________________________________
>> > 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
>
>
> _______________________________________________
> Wtr-development mailing list
> Wtr-development at rubyforge.org
> http://rubyforge.org/mailman/listinfo/wtr-development
>

From charley.baker at gmail.com  Thu Jul  7 13:38:29 2011
From: charley.baker at gmail.com (Charley Baker)
Date: Thu, 7 Jul 2011 11:38:29 -0600
Subject: [Wtr-development] suggestion: do not raise
 UnknownObjectException with #exists?
In-Reply-To: <CAHZHd6XRs=FyxPHYdF_PZxXPSUZRnYzyKAr5gCv1eKsw2T76bQ@mail.gmail.com>
References: <CAHZHd6WqoqDFMtzV-FXjz1JUY7q1zxzY1FP8AScO4FXv7GqQyA@mail.gmail.com>
	<CAPjkWY3tKovuUepmMYs_yrziX2bm9a-ygO8yGac5mYBrs=MTUQ@mail.gmail.com>
	<CAHZHd6VvAF5zk-GfdubiU3c2=cCSj=7xDBcgEsWk0y9hF0+-ww@mail.gmail.com>
	<CAOX+1PcbFRF7X-JK8B4Q1X1w976_br8pG4DPPb107XHf69Qkww@mail.gmail.com>
	<CAHZHd6XRs=FyxPHYdF_PZxXPSUZRnYzyKAr5gCv1eKsw2T76bQ@mail.gmail.com>
Message-ID: <CAOX+1PenzLtFRFg0DMfq7=RbVW3z=SORi39Mmz5-+KMoA1KV6w@mail.gmail.com>

That's odd, for some reason it seemed more challenging. Maybe I'm conflating
a few changes. The rest of the changes look like good ideas.


Cheers,

Charley



On Thu, Jul 7, 2011 at 11:31 AM, Jarmo <jarmo.p at gmail.com> wrote:

> Thanks for the challenge :P
>
> https://github.com/bret/watir/commit/4393747a6fb1ce698aa9c89fb36965985e8ddd28
>
> I'd like to make a new release soon with the following changes:
> * Bump RAutomation dependency version to 0.6.2 to:
>  - fix/improve Watir::IE#send_keys.
>  - fix Watir::IE loading for certain Windows XP environments
> (http://jira.openqa.org/browse/WTR-484).
> * Restored Watir::IE#autoit method to use RAutomation's AutoIt adapter
> with a deprecation warning.
> * Cache IE.version result to not access registry with each execution -
> was causing slowness in TextField#set for example.
> * Do not raise UnknownObjectException if parent element doesn't exist
> when calling Element#exists?
>
> Any objections?
>
> Jarmo
>
> On Thu, Jul 7, 2011 at 7:27 PM, Charley Baker <charley.baker at gmail.com>
> wrote:
> > I also think it's a great idea. I remember talking about it with Bret at
> one
> > point, and it was more challenging than it seemed at first glance. I've
> also
> > had to do the wait_until blocks with rescue for Ajaxy pages. exists?
> should
> > not explode imho.
> > Cheers,
> > Charley
> >
> >
> > On Thu, Jul 7, 2011 at 10:16 AM, Jarmo <jarmo.p at gmail.com> wrote:
> >>
> >> Haven't digged into technicalities yet. Just wanted to make sure that
> >> this behavior would make sense to everyone else too before starting to
> >> spend time on it.
> >>
> >> Jarmo
> >>
> >> On Thu, Jul 7, 2011 at 7:13 PM, Bret Pettichord <bret at pettichord.com>
> >> wrote:
> >> > I think I tried to do this years ago, but found it to be too
> difficult.
> >> > How
> >> > would you do it?
> >> >
> >> > Bret
> >> >
> >> > On Thu, Jul 7, 2011 at 10:17 AM, Jarmo <jarmo.p at gmail.com> wrote:
> >> >>
> >> >> Hi!
> >> >>
> >> >> Currently if there's some elements which doesn't exist, but will
> exist
> >> >> after some time (for example, after some ajax request), then i have
> to
> >> >> do something like this:
> >> >> browser.wait_until {div(:id => 'doesntexist').span(:class =>
> >> >> 'doesntexisteither').exists? rescue false}
> >> >> or
> >> >> browser.wait_until {div(:id => 'doesntexist').exists? && div(:id =>
> >> >> 'doesntexist).span(:class => 'doesntexisteither')}
> >> >>
> >> >> I don't like much both of the ways and started thinking that what if
> >> >> #exists? returned a boolean all the time? What if it returns false if
> >> >> the parent element doesn't exist instead of raising that unneeded
> >> >> exception? Since this would be a core change, i'd like to know what
> do
> >> >> you think and/or how do you handle situations like these in your
> >> >> tests?
> >> >>
> >> >> How does watir-webdriver handle these situations?
> >> >>
> >> >> Jarmo
> >> >> _______________________________________________
> >> >> Wtr-development mailing list
> >> >> Wtr-development at rubyforge.org
> >> >> http://rubyforge.org/mailman/listinfo/wtr-development
> >> >
> >> >
> >> >
> >> > --
> >> > Bret Pettichord
> >> > Director, Watir Project, www.watir.com
> >> >
> >> > Blog, www.testingwithvision.com
> >> > Twitter, www.twitter.com/bpettichord
> >> >
> >> >
> >> > _______________________________________________
> >> > 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
> >
> >
> > _______________________________________________
> > 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: <http://rubyforge.org/pipermail/wtr-development/attachments/20110707/d539e9e3/attachment.html>

From bret at pettichord.com  Thu Jul  7 22:15:18 2011
From: bret at pettichord.com (Bret Pettichord)
Date: Thu, 7 Jul 2011 21:15:18 -0500
Subject: [Wtr-development] suggestion: do not raise
 UnknownObjectException with #exists?
In-Reply-To: <CAHZHd6XRs=FyxPHYdF_PZxXPSUZRnYzyKAr5gCv1eKsw2T76bQ@mail.gmail.com>
References: <CAHZHd6WqoqDFMtzV-FXjz1JUY7q1zxzY1FP8AScO4FXv7GqQyA@mail.gmail.com>
	<CAPjkWY3tKovuUepmMYs_yrziX2bm9a-ygO8yGac5mYBrs=MTUQ@mail.gmail.com>
	<CAHZHd6VvAF5zk-GfdubiU3c2=cCSj=7xDBcgEsWk0y9hF0+-ww@mail.gmail.com>
	<CAOX+1PcbFRF7X-JK8B4Q1X1w976_br8pG4DPPb107XHf69Qkww@mail.gmail.com>
	<CAHZHd6XRs=FyxPHYdF_PZxXPSUZRnYzyKAr5gCv1eKsw2T76bQ@mail.gmail.com>
Message-ID: <CAPjkWY352z6urXSgQK0ipApuNrcyeVaB_iCCCggk3kmtrLGGaA@mail.gmail.com>

After I said that we thought fixing exists? would be hard, I wondered if
maybe we could just catch the error. I think there may have been a time
where we thought using rescue was cheating. Anyway +1 on the fix.

Should we depend on RAutomation 0.6.2 or rather ~> 0.6 so that we would
automatically pick up any later patches as well?

Bret

On Thu, Jul 7, 2011 at 12:31 PM, Jarmo <jarmo.p at gmail.com> wrote:

> Thanks for the challenge :P
>
> https://github.com/bret/watir/commit/4393747a6fb1ce698aa9c89fb36965985e8ddd28
>
> I'd like to make a new release soon with the following changes:
> * Bump RAutomation dependency version to 0.6.2 to:
>  - fix/improve Watir::IE#send_keys.
>  - fix Watir::IE loading for certain Windows XP environments
> (http://jira.openqa.org/browse/WTR-484).
> * Restored Watir::IE#autoit method to use RAutomation's AutoIt adapter
> with a deprecation warning.
> * Cache IE.version result to not access registry with each execution -
> was causing slowness in TextField#set for example.
> * Do not raise UnknownObjectException if parent element doesn't exist
> when calling Element#exists?
>
> Any objections?
>
> Jarmo
>
> On Thu, Jul 7, 2011 at 7:27 PM, Charley Baker <charley.baker at gmail.com>
> wrote:
> > I also think it's a great idea. I remember talking about it with Bret at
> one
> > point, and it was more challenging than it seemed at first glance. I've
> also
> > had to do the wait_until blocks with rescue for Ajaxy pages. exists?
> should
> > not explode imho.
> > Cheers,
> > Charley
> >
> >
> > On Thu, Jul 7, 2011 at 10:16 AM, Jarmo <jarmo.p at gmail.com> wrote:
> >>
> >> Haven't digged into technicalities yet. Just wanted to make sure that
> >> this behavior would make sense to everyone else too before starting to
> >> spend time on it.
> >>
> >> Jarmo
> >>
> >> On Thu, Jul 7, 2011 at 7:13 PM, Bret Pettichord <bret at pettichord.com>
> >> wrote:
> >> > I think I tried to do this years ago, but found it to be too
> difficult.
> >> > How
> >> > would you do it?
> >> >
> >> > Bret
> >> >
> >> > On Thu, Jul 7, 2011 at 10:17 AM, Jarmo <jarmo.p at gmail.com> wrote:
> >> >>
> >> >> Hi!
> >> >>
> >> >> Currently if there's some elements which doesn't exist, but will
> exist
> >> >> after some time (for example, after some ajax request), then i have
> to
> >> >> do something like this:
> >> >> browser.wait_until {div(:id => 'doesntexist').span(:class =>
> >> >> 'doesntexisteither').exists? rescue false}
> >> >> or
> >> >> browser.wait_until {div(:id => 'doesntexist').exists? && div(:id =>
> >> >> 'doesntexist).span(:class => 'doesntexisteither')}
> >> >>
> >> >> I don't like much both of the ways and started thinking that what if
> >> >> #exists? returned a boolean all the time? What if it returns false if
> >> >> the parent element doesn't exist instead of raising that unneeded
> >> >> exception? Since this would be a core change, i'd like to know what
> do
> >> >> you think and/or how do you handle situations like these in your
> >> >> tests?
> >> >>
> >> >> How does watir-webdriver handle these situations?
> >> >>
> >> >> Jarmo
> >> >> _______________________________________________
> >> >> Wtr-development mailing list
> >> >> Wtr-development at rubyforge.org
> >> >> http://rubyforge.org/mailman/listinfo/wtr-development
> >> >
> >> >
> >> >
> >> > --
> >> > Bret Pettichord
> >> > Director, Watir Project, www.watir.com
> >> >
> >> > Blog, www.testingwithvision.com
> >> > Twitter, www.twitter.com/bpettichord
> >> >
> >> >
> >> > _______________________________________________
> >> > 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
> >
> >
> > _______________________________________________
> > 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
>



-- 
Bret Pettichord
Director, Watir Project, www.watir.com

Blog, www.testingwithvision.com
Twitter, www.twitter.com/bpettichord
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/wtr-development/attachments/20110707/8de57132/attachment.html>

From watirjira at gmail.com  Fri Jul  8 11:53:50 2011
From: watirjira at gmail.com (Michael M (JIRA))
Date: Fri, 8 Jul 2011 10:53:50 -0500 (CDT)
Subject: [Wtr-development] [JIRA] Created: (WTR-485) Waitr fails to
	fire_event for select_list
Message-ID: <14447967.3.1310140430263.JavaMail.oqa-j2ee@openqa01.managed.contegix.com>

Waitr fails to fire_event for select_list
-----------------------------------------

                 Key: WTR-485
                 URL: http://jira.openqa.org/browse/WTR-485
             Project: Watir
          Issue Type: Bug
          Components: Inputs
    Affects Versions: 1.8.0
         Environment: Windows XP SP3 (64-bit), Internet Explorer 8.0.6001.18702 (32-bit)
            Reporter: Michael M
            Priority: Major


Watir is able to fire an event for a select list if there are events 
of the required type registered to the element. If, however, there are 
no objects registered via JavaScript to the select element, then it 
fails.

Versions: 
Ruby 1.9.2p180 
Watir 1.9.1.rc1

HTML Code Sample: 
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http:// 
www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> 
<html xmlns="http://www.w3.org/1999/xhtml"> 
  <head> 
    <title>fire event sample</title> 
 </head> 
  <body> 
    <select name="select"> 
      <option value="1">value1</option> 
      <option value="2">value2</option> 
    </select> 
  </body> 
</html>

Ruby Code Sample: 
require 'watir' 
browser = Watir::Browser.new 
browser.goto "http://<path.to>/testPage.html" 
browser.select_list(:name, 'select').fire_event('change')

Expected Result: 
Code should execute without any errors, firing events if there were
any, and otherwise doing nothing (just like the equivalent behaviour
in JavaScript).

Actual Result:
C:/Ruby192/lib/ruby/gems/1.9.1/gems/watir-1.9.1.rc1/lib/watir/
element.rb:339:in `method_missing': (in OLE method `fireEvent': )
(WIN32OLERuntimeError) 
    OLE error code:80070057 in htmlfile 
      Invalid argument. 
    HRESULT error code:0x80020009 
      Exception occurred. 
        from C:/Ruby192/lib/ruby/gems/1.9.1/gems/watir-1.9.1.rc1/lib/ 
watir/element.rb:339:in `dispatch_event' 
        from C:/Ruby192/lib/ruby/gems/1.9.1/gems/watir-1.9.1.rc1/lib/ 
watir/element.rb:325:in `fire_event' 
        from IE8FireEventBug.rb:21:in `<main>' 

-- 
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 jarmo.p at gmail.com  Fri Jul  8 16:41:00 2011
From: jarmo.p at gmail.com (Jarmo)
Date: Fri, 8 Jul 2011 23:41:00 +0300
Subject: [Wtr-development] suggestion: do not raise
 UnknownObjectException with #exists?
In-Reply-To: <CAPjkWY352z6urXSgQK0ipApuNrcyeVaB_iCCCggk3kmtrLGGaA@mail.gmail.com>
References: <CAHZHd6WqoqDFMtzV-FXjz1JUY7q1zxzY1FP8AScO4FXv7GqQyA@mail.gmail.com>
	<CAPjkWY3tKovuUepmMYs_yrziX2bm9a-ygO8yGac5mYBrs=MTUQ@mail.gmail.com>
	<CAHZHd6VvAF5zk-GfdubiU3c2=cCSj=7xDBcgEsWk0y9hF0+-ww@mail.gmail.com>
	<CAOX+1PcbFRF7X-JK8B4Q1X1w976_br8pG4DPPb107XHf69Qkww@mail.gmail.com>
	<CAHZHd6XRs=FyxPHYdF_PZxXPSUZRnYzyKAr5gCv1eKsw2T76bQ@mail.gmail.com>
	<CAPjkWY352z6urXSgQK0ipApuNrcyeVaB_iCCCggk3kmtrLGGaA@mail.gmail.com>
Message-ID: <CAHZHd6WZPf2mCAoOyR-jBhrgi2UfFePYbjc38psF_sdd9hMVDQ@mail.gmail.com>

hehe @ cheating.

Currently it's ~> 0.6.2, which means that it will pick up updates
until 0.7.0, which is good thing i guess since i'm trying to follow
semver (http://semver.org/) guidelines. I'm not sure if ~> 0.6 would
be needed, i'll think about it.

Jarmo

On Fri, Jul 8, 2011 at 5:15 AM, Bret Pettichord <bret at pettichord.com> wrote:
> After I said that we thought fixing exists? would be hard, I wondered if
> maybe we could just catch the error. I think there may have been a time
> where we thought using rescue was cheating. Anyway +1 on the fix.
>
> Should we depend on RAutomation 0.6.2 or rather ~> 0.6 so that we would
> automatically pick up any later patches as well?
>
> Bret
>
> On Thu, Jul 7, 2011 at 12:31 PM, Jarmo <jarmo.p at gmail.com> wrote:
>>
>> Thanks for the challenge :P
>>
>> https://github.com/bret/watir/commit/4393747a6fb1ce698aa9c89fb36965985e8ddd28
>>
>> I'd like to make a new release soon with the following changes:
>> * Bump RAutomation dependency version to 0.6.2 to:
>> ?- fix/improve Watir::IE#send_keys.
>> ?- fix Watir::IE loading for certain Windows XP environments
>> (http://jira.openqa.org/browse/WTR-484).
>> * Restored Watir::IE#autoit method to use RAutomation's AutoIt adapter
>> with a deprecation warning.
>> * Cache IE.version result to not access registry with each execution -
>> was causing slowness in TextField#set for example.
>> * Do not raise UnknownObjectException if parent element doesn't exist
>> when calling Element#exists?
>>
>> Any objections?
>>
>> Jarmo
>>
>> On Thu, Jul 7, 2011 at 7:27 PM, Charley Baker <charley.baker at gmail.com>
>> wrote:
>> > I also think it's a great idea. I remember talking about it with Bret at
>> > one
>> > point, and it was more challenging than it seemed at first glance. I've
>> > also
>> > had to do the wait_until blocks with rescue for Ajaxy pages. exists?
>> > should
>> > not explode imho.
>> > Cheers,
>> > Charley
>> >
>> >
>> > On Thu, Jul 7, 2011 at 10:16 AM, Jarmo <jarmo.p at gmail.com> wrote:
>> >>
>> >> Haven't digged into technicalities yet. Just wanted to make sure that
>> >> this behavior would make sense to everyone else too before starting to
>> >> spend time on it.
>> >>
>> >> Jarmo
>> >>
>> >> On Thu, Jul 7, 2011 at 7:13 PM, Bret Pettichord <bret at pettichord.com>
>> >> wrote:
>> >> > I think I tried to do this years ago, but found it to be too
>> >> > difficult.
>> >> > How
>> >> > would you do it?
>> >> >
>> >> > Bret
>> >> >
>> >> > On Thu, Jul 7, 2011 at 10:17 AM, Jarmo <jarmo.p at gmail.com> wrote:
>> >> >>
>> >> >> Hi!
>> >> >>
>> >> >> Currently if there's some elements which doesn't exist, but will
>> >> >> exist
>> >> >> after some time (for example, after some ajax request), then i have
>> >> >> to
>> >> >> do something like this:
>> >> >> browser.wait_until {div(:id => 'doesntexist').span(:class =>
>> >> >> 'doesntexisteither').exists? rescue false}
>> >> >> or
>> >> >> browser.wait_until {div(:id => 'doesntexist').exists? && div(:id =>
>> >> >> 'doesntexist).span(:class => 'doesntexisteither')}
>> >> >>
>> >> >> I don't like much both of the ways and started thinking that what if
>> >> >> #exists? returned a boolean all the time? What if it returns false
>> >> >> if
>> >> >> the parent element doesn't exist instead of raising that unneeded
>> >> >> exception? Since this would be a core change, i'd like to know what
>> >> >> do
>> >> >> you think and/or how do you handle situations like these in your
>> >> >> tests?
>> >> >>
>> >> >> How does watir-webdriver handle these situations?
>> >> >>
>> >> >> Jarmo
>> >> >> _______________________________________________
>> >> >> Wtr-development mailing list
>> >> >> Wtr-development at rubyforge.org
>> >> >> http://rubyforge.org/mailman/listinfo/wtr-development
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > Bret Pettichord
>> >> > Director, Watir Project, www.watir.com
>> >> >
>> >> > Blog, www.testingwithvision.com
>> >> > Twitter, www.twitter.com/bpettichord
>> >> >
>> >> >
>> >> > _______________________________________________
>> >> > 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
>> >
>> >
>> > _______________________________________________
>> > 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
>
>
>
> --
> Bret Pettichord
> Director, Watir Project, www.watir.com
>
> Blog, www.testingwithvision.com
> Twitter, www.twitter.com/bpettichord
>
>
> _______________________________________________
> Wtr-development mailing list
> Wtr-development at rubyforge.org
> http://rubyforge.org/mailman/listinfo/wtr-development
>

From watirjira at gmail.com  Sat Jul  9 08:19:51 2011
From: watirjira at gmail.com (Jarmo Pertman (JIRA))
Date: Sat, 9 Jul 2011 07:19:51 -0500 (CDT)
Subject: [Wtr-development] [JIRA] Commented: (WTR-397) How to speed up text
	field data entry
Message-ID: <15810664.7.1310213991107.JavaMail.oqa-j2ee@openqa01.managed.contegix.com>


    [ http://jira.openqa.org/browse/WTR-397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20230#action_20230 ] 

Jarmo Pertman commented on WTR-397:
-----------------------------------

I looked into that issue and noticed that most time is spent for invoking javascript key press events and then waiting for them to complete. I'm not sure if IE-Watir waits for them to complete or not, but i tried with commenting out "wait() if wait" line in firewatir/element.rb:
https://github.com/bret/watir/blob/master/firewatir/lib/firewatir/element.rb#L897

That managed to speed up the text entry 2-3 times. It is still a lot slower than IE-Watir though. It just seems that invoking those events itself is also slower due to the fact that after each event a result is read back (if that would be omitted then i saw other strange failures).

If i commented out the abovementioned "wait" line then all firewatir tests were passing to me. I wonder if that means that there isn't any test, which could provide the situation where it might fail or if we could actually omit that line at all. Any thoughts?

> How to speed up text field data entry
> -------------------------------------
>
>                 Key: WTR-397
>                 URL: http://jira.openqa.org/browse/WTR-397
>             Project: Watir
>          Issue Type: Bug
>          Components: FireWatir
>    Affects Versions: Open QA Migration
>         Environment: windows
>            Reporter: Zeljko
>
> - moved from http://code.google.com/p/firewatir/issues/detail?id=78
> Issue 78:	How to speed up text field data entry
> 4 people starred this issue and may be notified of changes.
> Status: 	New
> Owner: 	 ----
> Type-Defect
> Priority-Medium
> Reported by restagner, Aug 11, 2008
> What steps will reproduce the problem?
> 1. Create identical scripts for Watir/Firewatir that use data entry into
> text fields
> 2. Execute scripts
> What is the expected output? What do you see instead?
> I'd like to see the same speed/performance that Watir provides.
> What version of the product are you using? On what operating system?
> firewatir-1.2.0, Windows XP
> Please provide any additional information below.
> I'm using both Watir and FireWatir.  I've developed a script that
> works well with both APIs.  However, it seems that when the script is
> executed in FireWatir, the speed with which data is entered into text
> fields is *really* slow.  Anybody out there know how I can speed up
> data entry into text fields for FireWatir. I've tried using
> text_field.value='my value'
> instead of
> text_field.set 'my value'
> However, it appears that using .value= results in the script missing
> some of the web app's triggering events.  Any help on this would be
> greatly appreciated.
> Regards,
> Robert 
> ---
> Comment 1 by robblovell, Aug 25, 2008
> I have noticed VERY slow text entry on a windows Server 2003 box with firefox
> 2.0.0.16 and firewatir 1.2.1 (it also ran slow with 1.1.1) and jssh-WINNT-2.x.xpi. 
> The code runs from a ruby-rails application. The same code works fast on os/x with
> the same firefox/firewatir versions.  I have a linux install as well, with a self
> built version of firefox 3.0 with jssh following the instructions here:
> (http://ubuntu-snippets.blogspot.com/2008/07/build-firefox-3-web-browser-with-jssh.html).
> This setup also runs very slowly at times for text entry with firewatir 1.2.0.
> The behavior isn't consistent, sometimes it runs at normal speed, sometimes in super
> slow-mo.
> Any help or clues would be appreciated as to why firewatir-jssh/firefox may run super
> slow.
> ---
> Comment 2 by robblovell, Aug 25, 2008
> here is another person who experienced a slow down:
> http://www.io.com/~wazmo/blog/archives/2007_11.html
> ---
> Comment 3 by talksense101, May 12, 2009
> I use ruby 1.8.7 on Windows with Firefox 3.0.10 and the current version of Firewatir
> as on May 12,2009.  Same issue with text_field.set "xyz".  It is too slow.
> ---
> Comment 4 by juliomonteiro, Sep 17, 2009
> Really slow. My SafariWatir (Mac OS X 10.6 + Safari) needs 50 seconds to run a bunch of tests, which FireWatir (at 
> Ubuntu 9.04 + Firefox 3) needs 5 minutes.

-- 
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 Jul  9 08:27:50 2011
From: watirjira at gmail.com (Jarmo Pertman (JIRA))
Date: Sat, 9 Jul 2011 07:27:50 -0500 (CDT)
Subject: [Wtr-development] [JIRA] Closed: (WTR-478) highlight method was
 broken in watir 1.6.7+
In-Reply-To: <26414056.179.1306482732792.JavaMail.oqa-j2ee@openqa01.managed.contegix.com>
Message-ID: <33327641.9.1310214470138.JavaMail.oqa-j2ee@openqa01.managed.contegix.com>


     [ http://jira.openqa.org/browse/WTR-478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jarmo Pertman closed WTR-478.
-----------------------------

       Resolution: Fixed
    Fix Version/s: Soon

fixed, thanks :)
https://github.com/bret/watir/commit/186f9338629250509e52807d957256d7b507ced9

> highlight method was broken in watir 1.6.7+
> -------------------------------------------
>
>                 Key: WTR-478
>                 URL: http://jira.openqa.org/browse/WTR-478
>             Project: Watir
>          Issue Type: Bug
>          Components: Wait
>    Affects Versions: 1.6.7, 1.8.0
>         Environment: Windows XP/IE 6, Windows 7/IE 9
>            Reporter: Sergey Erokhin
>             Fix For: Soon
>
>
> method highlit doesn't work in watir 1.6.7+
> style.backgroundColor - redonly?
> watir 1.8.1
> i try to investigate
> in element.rb
> 206        begin
> 207          @original_color ||= style.backgroundColor
> 208          style.backgroundColor = @container.activeObjectHighLightColor
> 209        rescue
> 210          @original_color = nil
> 211        end
> when i comment line 209 and 210
> result
> C:/Ruby/lib/ruby/gems/1.8/gems/watir-1.8.1/lib/watir/element.rb:208:in `method_missing':  (WIN32OLERuntimeError)
>     OLE error code:0 in <Unknown>
>       <No Description>
>     HRESULT error code:0x80020003
>       Member not found.
>         from C:/Ruby/lib/ruby/gems/1.8/gems/watir-1.8.1/lib/watir/element.rb:208:in `highlight'
>         from C:/Ruby/lib/ruby/gems/1.8/gems/watir-1.8.1/lib/watir/input_elements.rb:370:in `set'
>         from test_hightlit.rb:9
> source code
> 1.6.7+
>     def_wrap_guard :currentstyle
>     # return current style instead of the inline style of the element
>     alias style currentstyle
> 1.6.5
>     # return the style of the element
>     def_wrap_guard :style
> my fix (i am not quite sure about absolute correctnes)
> replace
>     alias style currentstyle
> to
>     def_wrap_guard :style
> it works for me on both configuration.
> bug introduced in commmit https://github.com/bret/watir/commit/ebf38031c92c800ca0b0897706d10d9c4240a4a7#watir/lib/watir/element.rb

-- 
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 jarmo.p at gmail.com  Sat Jul  9 08:35:43 2011
From: jarmo.p at gmail.com (Jarmo)
Date: Sat, 9 Jul 2011 15:35:43 +0300
Subject: [Wtr-development] Released Watir 1.9.2.rc1
Message-ID: <CAHZHd6UWo-z0E=ZP67m-va62Q4S5nu2s1CtuZoPeLNiJJDCkPg@mail.gmail.com>

Hi!

Just released Watir 1.9.2.rc1. Install it with "gem install watir --pre".

There are only IE changes this time, sorry FireWatir users:
* Bump RAutomation dependency version to 0.6.2 to:
 - fix/improve Watir::IE#send_keys.
 - fix Watir::IE loading for certain Windows XP environments
(http://jira.openqa.org/browse/WTR-484).
* Restored Watir::IE#autoit method to use RAutomation's AutoIt adapter
with a deprecation warning.
* Cache IE.version result to not access registry with each execution -
was causing slowness in TextField#set for example.
* Do not raise UnknownObjectException if parent element doesn't exist
when calling Element#exists?
* Element#flash highlights elements again
(http://jira.openqa.org/browse/WTR-478)

Try to run your current tests with this version and let us know of the results.

Thank you!

Jarmo

From jarmo.p at gmail.com  Mon Jul 11 12:43:11 2011
From: jarmo.p at gmail.com (Jarmo)
Date: Mon, 11 Jul 2011 19:43:11 +0300
Subject: [Wtr-development] Released Watir 1.9.2
Message-ID: <CAHZHd6UE8y=rYdfqomPJ0N9yr58XpY8=77m8tvv3rzggzYZXvQ@mail.gmail.com>

Hi!

We're into frequent releases - just released Watir 1.9.2. Install it
with "gem install watir".

There are only IE changes this time, sorry FireWatir users:
* Bump RAutomation dependency version to 0.6.2 to:
 - fix/improve Watir::IE#send_keys.
 - fix Watir::IE loading for certain Windows XP environments
(http://jira.openqa.org/browse/WTR-484).
* Restored Watir::IE#autoit method to use RAutomation's AutoIt adapter
with a deprecation warning.
* Cache IE.version result to not access registry with each execution -
was causing slowness in TextField#set for example.
* Do not raise UnknownObjectException if parent element doesn't exist
when calling Element#exists?
* Element#flash highlights elements again
(http://jira.openqa.org/browse/WTR-478)

Thank you!

Jarmo

From bret at pettichord.com  Mon Jul 11 12:53:17 2011
From: bret at pettichord.com (Bret Pettichord)
Date: Mon, 11 Jul 2011 11:53:17 -0500
Subject: [Wtr-development] Released Watir 1.9.2
In-Reply-To: <CAHZHd6UE8y=rYdfqomPJ0N9yr58XpY8=77m8tvv3rzggzYZXvQ@mail.gmail.com>
References: <CAHZHd6UE8y=rYdfqomPJ0N9yr58XpY8=77m8tvv3rzggzYZXvQ@mail.gmail.com>
Message-ID: <CAPjkWY0Gha-NtfbQM3zkUnKLcEpu7bE0pfCXF3e51roH5uK6KQ@mail.gmail.com>

Awesome.

On Mon, Jul 11, 2011 at 11:43 AM, Jarmo <jarmo.p at gmail.com> wrote:

> Hi!
>
> We're into frequent releases - just released Watir 1.9.2. Install it
> with "gem install watir".
>
> There are only IE changes this time, sorry FireWatir users:
> * Bump RAutomation dependency version to 0.6.2 to:
>  - fix/improve Watir::IE#send_keys.
>  - fix Watir::IE loading for certain Windows XP environments
> (http://jira.openqa.org/browse/WTR-484).
> * Restored Watir::IE#autoit method to use RAutomation's AutoIt adapter
> with a deprecation warning.
> * Cache IE.version result to not access registry with each execution -
> was causing slowness in TextField#set for example.
> * Do not raise UnknownObjectException if parent element doesn't exist
> when calling Element#exists?
> * Element#flash highlights elements again
> (http://jira.openqa.org/browse/WTR-478)
>
> Thank you!
>
> Jarmo
> _______________________________________________
> Wtr-development mailing list
> Wtr-development at rubyforge.org
> http://rubyforge.org/mailman/listinfo/wtr-development
>



-- 
Bret Pettichord
Director, Watir Project, www.watir.com

Blog, www.testingwithvision.com
Twitter, www.twitter.com/bpettichord
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/wtr-development/attachments/20110711/0611d052/attachment.html>

From watirjira at gmail.com  Mon Jul 11 13:04:51 2011
From: watirjira at gmail.com (Jarmo Pertman (JIRA))
Date: Mon, 11 Jul 2011 12:04:51 -0500 (CDT)
Subject: [Wtr-development] [JIRA] Commented: (WTR-481) Not able to open new
 IE after it is closed.
In-Reply-To: <31083542.38.1307636456038.JavaMail.oqa-j2ee@openqa01.managed.contegix.com>
Message-ID: <32779085.27.1310403891752.JavaMail.oqa-j2ee@openqa01.managed.contegix.com>


    [ http://jira.openqa.org/browse/WTR-481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20233#action_20233 ] 

Jarmo Pertman commented on WTR-481:
-----------------------------------

Oh crap. This seems to be more of a bug in Ruby 1.9... Ethan do you know if that happens with every WIN32OLERuntimeError or only with some specific ones?

> Not able to open new IE after it is closed.
> -------------------------------------------
>
>                 Key: WTR-481
>                 URL: http://jira.openqa.org/browse/WTR-481
>             Project: Watir
>          Issue Type: Bug
>          Components: Unit Tests
>    Affects Versions: Soon
>         Environment: Windows XP running IE7
>            Reporter: bhavesh
>            Priority: Critical
>             Fix For: Soon
>
>
> Hi, 
> I have to close IE and open new IE  again in every testcase. 
> I written an routine like this : 
>   def setupnew(current_component="") 
>         $ie.close if $ie 
>         sleep(10) 
>         $ie = Watir::IE.new() 
>         sleep(10) 
>         case current_component 
>                   when "WEB_ADMIN" 
>                           $ie.goto($adminLink) 
>                   when "WEB_REPORT" 
>                           $ie.goto($reportLink) 
>                   when "WEB_SEARCH" 
>                           $ie.goto($searchLink) 
>                   else 
>                           #puts "Setup case does not match" 
>         end 
>   end 
> This works well in Ruby 1.8 
> Recently i upgrade to Ruby 1.9.2 and this routine start failing. 
> It closes the IE if it is open but then not opening the new IE  it 
> just came out of script throwing error. 
> Error coming out as : 
>     TestCaseNum: I18N_0001 
>     Description: Add AD Authentication  from Webadmin, for FIGS. 
> E 
> Finished in 0.468750 seconds. 
>   1) Error: 
> test_0001(TC_I18N): 
> NoMethodError: unknown property or method: `name' 
>     HRESULT error code:0x800706ba 
>       The RPC server is unavailable. 
>     C:/Ruby192/lib/ruby/gems/1.9.1/gems/watir-1.8.1/lib/watir/ie- 
> class.rb:319:in 
>  `method_missing' 
>     C:/Ruby192/lib/ruby/gems/1.9.1/gems/watir-1.8.1/lib/watir/ie- 
> class.rb:319:in 
>  `exists?' 
>     C:/Ruby192/lib/ruby/gems/1.9.1/gems/watir-1.8.1/lib/watir/ie- 
> class.rb:406:in 
>  `close' 
>     C:/IE_AUTOMATION/kazeon/qa/watir-v1_4-TIP/KazModules/I18N/ 
> I18N_Regression.rb 
> :47:in `setupnew' 
>     C:/IE_AUTOMATION/kazeon/qa/watir-v1_4-TIP/KazModules/I18N/ 
> I18N_Regression.rb 
> :102:in `test_0001' 
>  got the problem but not the solution. 
> In watir 1.6.7 which i use previously, code for ie.close is like 
> this : 
> #C:\ruby\lib\ruby\gems\1.8\gems\watir-1.6.7\lib\watir 
>     # Closes the Browser 
>     def close 
>       return unless exists? 
>       @closing = true 
>       @ie.stop 
>       wait rescue nil 
>       chwnd = @ie.hwnd.to_i 
>       @ie.quit 
>       while Win32API.new("user32","IsWindow", 'L', 'L').Call(chwnd) == 
> 1 
>         sleep 0.3 
>       end 
>     end 
> In watir 1.8.1 which i use now, code for ie.close is like this : 
> C:\Ruby192\lib\ruby\gems\1.9.1\gems\watir-1.8.1\lib\watir 
>     # Closes the Browser 
>     def close 
>       return unless exists? 
>       @ie.stop 
>       wait rescue nil 
>       chwnd = @ie.hwnd.to_i 
>       @ie.quit 
>       t = Time.now 
>       while exists? 
>         # just in case to avoid possible endless loop if failing to 
> close some 
>         # window or tab 
>         break if Time.now - t > 10 
>         sleep 0.3 
>       end 
>     end 
> There is an change in code in 1.8.1. 
> If i replace the piece of code for ie.close of version 1.6.7  in 1.8.1 
> file, the same routine starts working fine. 
> So what needs to be done now to have this working with 1.8.1 code? 
> Bhavesh 

-- 
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 Jul 11 13:12:50 2011
From: watirjira at gmail.com (Ethan (JIRA))
Date: Mon, 11 Jul 2011 12:12:50 -0500 (CDT)
Subject: [Wtr-development] [JIRA] Commented: (WTR-481) Not able to open new
 IE after it is closed.
In-Reply-To: <31083542.38.1307636456038.JavaMail.oqa-j2ee@openqa01.managed.contegix.com>
Message-ID: <13157280.29.1310404370868.JavaMail.oqa-j2ee@openqa01.managed.contegix.com>


    [ http://jira.openqa.org/browse/WTR-481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20234#action_20234 ] 

Ethan commented on WTR-481:
---------------------------

It's not a bug in ruby. It's an intentional change in WIN32OLE - when an OLE object doesn't have a property and you attempt to call to that property, it raises NoMethodError, whereas it used to raise WIN32OLERuntimeError. NoMethodError is a sensible thing to raise in that case, I think. Nothing new is being raised; just a different exception class, so if in watir you change any "rescue WIN32OLERuntimeError" to "rescue WIN32OLERuntimeError, NoMethodError" then everything should work the same. 

> Not able to open new IE after it is closed.
> -------------------------------------------
>
>                 Key: WTR-481
>                 URL: http://jira.openqa.org/browse/WTR-481
>             Project: Watir
>          Issue Type: Bug
>          Components: Unit Tests
>    Affects Versions: Soon
>         Environment: Windows XP running IE7
>            Reporter: bhavesh
>            Priority: Critical
>             Fix For: Soon
>
>
> Hi, 
> I have to close IE and open new IE  again in every testcase. 
> I written an routine like this : 
>   def setupnew(current_component="") 
>         $ie.close if $ie 
>         sleep(10) 
>         $ie = Watir::IE.new() 
>         sleep(10) 
>         case current_component 
>                   when "WEB_ADMIN" 
>                           $ie.goto($adminLink) 
>                   when "WEB_REPORT" 
>                           $ie.goto($reportLink) 
>                   when "WEB_SEARCH" 
>                           $ie.goto($searchLink) 
>                   else 
>                           #puts "Setup case does not match" 
>         end 
>   end 
> This works well in Ruby 1.8 
> Recently i upgrade to Ruby 1.9.2 and this routine start failing. 
> It closes the IE if it is open but then not opening the new IE  it 
> just came out of script throwing error. 
> Error coming out as : 
>     TestCaseNum: I18N_0001 
>     Description: Add AD Authentication  from Webadmin, for FIGS. 
> E 
> Finished in 0.468750 seconds. 
>   1) Error: 
> test_0001(TC_I18N): 
> NoMethodError: unknown property or method: `name' 
>     HRESULT error code:0x800706ba 
>       The RPC server is unavailable. 
>     C:/Ruby192/lib/ruby/gems/1.9.1/gems/watir-1.8.1/lib/watir/ie- 
> class.rb:319:in 
>  `method_missing' 
>     C:/Ruby192/lib/ruby/gems/1.9.1/gems/watir-1.8.1/lib/watir/ie- 
> class.rb:319:in 
>  `exists?' 
>     C:/Ruby192/lib/ruby/gems/1.9.1/gems/watir-1.8.1/lib/watir/ie- 
> class.rb:406:in 
>  `close' 
>     C:/IE_AUTOMATION/kazeon/qa/watir-v1_4-TIP/KazModules/I18N/ 
> I18N_Regression.rb 
> :47:in `setupnew' 
>     C:/IE_AUTOMATION/kazeon/qa/watir-v1_4-TIP/KazModules/I18N/ 
> I18N_Regression.rb 
> :102:in `test_0001' 
>  got the problem but not the solution. 
> In watir 1.6.7 which i use previously, code for ie.close is like 
> this : 
> #C:\ruby\lib\ruby\gems\1.8\gems\watir-1.6.7\lib\watir 
>     # Closes the Browser 
>     def close 
>       return unless exists? 
>       @closing = true 
>       @ie.stop 
>       wait rescue nil 
>       chwnd = @ie.hwnd.to_i 
>       @ie.quit 
>       while Win32API.new("user32","IsWindow", 'L', 'L').Call(chwnd) == 
> 1 
>         sleep 0.3 
>       end 
>     end 
> In watir 1.8.1 which i use now, code for ie.close is like this : 
> C:\Ruby192\lib\ruby\gems\1.9.1\gems\watir-1.8.1\lib\watir 
>     # Closes the Browser 
>     def close 
>       return unless exists? 
>       @ie.stop 
>       wait rescue nil 
>       chwnd = @ie.hwnd.to_i 
>       @ie.quit 
>       t = Time.now 
>       while exists? 
>         # just in case to avoid possible endless loop if failing to 
> close some 
>         # window or tab 
>         break if Time.now - t > 10 
>         sleep 0.3 
>       end 
>     end 
> There is an change in code in 1.8.1. 
> If i replace the piece of code for ie.close of version 1.6.7  in 1.8.1 
> file, the same routine starts working fine. 
> So what needs to be done now to have this working with 1.8.1 code? 
> Bhavesh 

-- 
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 alister.scott at gmail.com  Thu Jul 14 21:28:01 2011
From: alister.scott at gmail.com (Alister Scott)
Date: Fri, 15 Jul 2011 11:28:01 +1000
Subject: [Wtr-development] Including Watir-WebDriver into Watir?
Message-ID: <CAC1iRBzUi42rEv2YXPaPKgxju78an3sb4bfMpwHBomPCGAsrhg@mail.gmail.com>

Hi,

What would be needed to get to a point where Watir-Webdriver was fully
included in Watir?

Watir would choose the best driver for the platform and browser. For
example, on Windows and IE, this would be the native Watir driver, on
Mac-Chrome, this would be ChromeDriver.

I understand the biggest difference is the zero based indexing, but I don't
think there has been any work since October last year on this:
https://github.com/bret/watir/tree/zero-index

What I would love to see one gem "watir" that provides all the necessary
drivers easily configurable for all platforms. We could then have unified
documentation on watir.com that easily shows how to use this.

Am I being too ambitious? What needs to be done?

Cheers,
Alister

Alister Scott
Brisbane, Australia
Watir Web Master: http://watir.com
Blog: http://watirmelon.com
LinkedIn: http://www.linkedin.com/in/alisterscott

"There are two ways to get enough: One is to continue to accumulate more and
more. The other is to desire less." *~ G. K. Chesterton*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/wtr-development/attachments/20110715/941ca079/attachment.html>

From bret at pettichord.com  Fri Jul 15 17:11:55 2011
From: bret at pettichord.com (Bret Pettichord)
Date: Fri, 15 Jul 2011 16:11:55 -0500
Subject: [Wtr-development] Including Watir-WebDriver into Watir?
In-Reply-To: <CAC1iRBzUi42rEv2YXPaPKgxju78an3sb4bfMpwHBomPCGAsrhg@mail.gmail.com>
References: <CAC1iRBzUi42rEv2YXPaPKgxju78an3sb4bfMpwHBomPCGAsrhg@mail.gmail.com>
Message-ID: <CAPjkWY1gKsVPP0Sz9RtKE2JV=Ey9yq==hNW-JU8iDuNRdn-cUA@mail.gmail.com>

The zero-index work needs to be finished, like you said.

The big issue the remains open is the ownership and interface for
Watir::Browser. Watir and Watir-Webdriver have conflicting versions of this
module/class. Watir's version (actually in common-watir) is pluggable to use
different implementations of watir-compatable drivers. Watir-WebDriver's
assumes you are using webdriver for all browsers. What I would like to see
would be for Watir-Webdriver to rename its class and then update
Watir::Browser to user Watir-Webdriver as the default implementation for
Firefox and perhaps others.

To make this really work, we'd also have to pull the Watir::IE
implementation out of the watir gem (creating a new gem ie-watir), so that
it was an optional component of watir -- and of course one that would only
be an option for Windows.

There are also lots of other packaging issues, but I think these are big
boulders.

Bret

On Thu, Jul 14, 2011 at 8:28 PM, Alister Scott <alister.scott at gmail.com>wrote:

> Hi,
>
> What would be needed to get to a point where Watir-Webdriver was fully
> included in Watir?
>
> Watir would choose the best driver for the platform and browser. For
> example, on Windows and IE, this would be the native Watir driver, on
> Mac-Chrome, this would be ChromeDriver.
>
> I understand the biggest difference is the zero based indexing, but I don't
> think there has been any work since October last year on this:
> https://github.com/bret/watir/tree/zero-index
>
> What I would love to see one gem "watir" that provides all the necessary
> drivers easily configurable for all platforms. We could then have unified
> documentation on watir.com that easily shows how to use this.
>
> Am I being too ambitious? What needs to be done?
>
> Cheers,
> Alister
>
> Alister Scott
> Brisbane, Australia
> Watir Web Master: http://watir.com
> Blog: http://watirmelon.com
> LinkedIn: http://www.linkedin.com/in/alisterscott
>
> "There are two ways to get enough: One is to continue to accumulate more
> and more. The other is to desire less." *~ G. K. Chesterton*
>
> _______________________________________________
> Wtr-development mailing list
> Wtr-development at rubyforge.org
> http://rubyforge.org/mailman/listinfo/wtr-development
>



-- 
Bret Pettichord
Director, Watir Project, www.watir.com

Blog, www.testingwithvision.com
Twitter, www.twitter.com/bpettichord
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/wtr-development/attachments/20110715/8cbaccae/attachment.html>

From watirjira at gmail.com  Fri Jul 15 17:39:51 2011
From: watirjira at gmail.com (Michael M (JIRA))
Date: Fri, 15 Jul 2011 16:39:51 -0500 (CDT)
Subject: [Wtr-development] [JIRA] Resolved: (WTR-483) Watir broken -
 Watir::Browser.new fails on Windows XP with IE 8
In-Reply-To: <256942.34.1309800669927.JavaMail.oqa-j2ee@openqa01.managed.contegix.com>
Message-ID: <18228749.44.1310765991586.JavaMail.oqa-j2ee@openqa01.managed.contegix.com>


     [ http://jira.openqa.org/browse/WTR-483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael M resolved WTR-483.
---------------------------

       Resolution: Fixed
    Fix Version/s:     (was: Soon)
                   1.9.2

rautomation 0.6.2 did fix this issue! Thanks for looking into it for me!

> Watir broken - Watir::Browser.new fails on Windows XP with IE 8
> ---------------------------------------------------------------
>
>                 Key: WTR-483
>                 URL: http://jira.openqa.org/browse/WTR-483
>             Project: Watir
>          Issue Type: Bug
>          Components: Frame, Other, Project Support, Window Attachment
>    Affects Versions: 1.8.0
>         Environment: Windows XP Pro x64 SP2
>            Reporter: Michael M
>            Priority: Blocker
>             Fix For: 1.9.2
>
>
> ruby 1.9.2p180 (2011-02-18) [i386-mingw32]
> watir (1.9.1)
> commonwatir (1.9.1)
> A very simple script no longer runs at all, not much else to say:
> require 'watir'
> browser = Watir::Browser.new
> browser.goto 'http://www.google.ca'
> The following exception occurs:
> C:/Ruby192/lib/ruby/gems/1.9.1/gems/commonwatir-1.9.1/lib/watir/browser.rb:89:in `eval': undefined method `class_eval' for [["RAutomation"]]:Array (NoMethodError)
>         from C:/Ruby192/lib/ruby/gems/1.9.1/gems/rautomation-0.6.0/lib/rautomation/element_collections.rb:8:in `each'
>         from C:/Ruby192/lib/ruby/gems/1.9.1/gems/rautomation-0.6.0/lib/rautomation/element_collections.rb:8:in `has_many'
>         from C:/Ruby192/lib/ruby/gems/1.9.1/gems/rautomation-0.6.0/lib/rautomation/window.rb:15:in `<class:Window>'
>         from C:/Ruby192/lib/ruby/gems/1.9.1/gems/rautomation-0.6.0/lib/rautomation/window.rb:11:in `<module:RAutomation>'
>         from C:/Ruby192/lib/ruby/gems/1.9.1/gems/rautomation-0.6.0/lib/rautomation/window.rb:1:in `<top (required)>'
>         from C:/Ruby192/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
>         from C:/Ruby192/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
>         from C:/Ruby192/lib/ruby/gems/1.9.1/gems/rautomation-0.6.0/lib/rautomation.rb:6:in `<top (required)>'
>         from C:/Ruby192/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
>         from C:/Ruby192/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
>         from C:/Ruby192/lib/ruby/gems/1.9.1/gems/watir-1.9.1/lib/watir/core.rb:36:in `<top (required)>'
>         from C:/Ruby192/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
>         from C:/Ruby192/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
>         from C:/Ruby192/lib/ruby/gems/1.9.1/gems/watir-1.9.1/lib/watir/ie.rb:2:in `<top (required)>'
>         from (eval):1:in `klass'
>         from C:/Ruby192/lib/ruby/gems/1.9.1/gems/commonwatir-1.9.1/lib/watir/browser.rb:89:in `eval'
>         from C:/Ruby192/lib/ruby/gems/1.9.1/gems/commonwatir-1.9.1/lib/watir/browser.rb:89:in `klass'
>         from C:/Ruby192/lib/ruby/gems/1.9.1/gems/commonwatir-1.9.1/lib/watir/browser.rb:79:in `set_options'
>         from C:/Ruby192/lib/ruby/gems/1.9.1/gems/commonwatir-1.9.1/lib/watir/browser.rb:142:in `set_sub_options'
>         from C:/Ruby192/lib/ruby/gems/1.9.1/gems/commonwatir-1.9.1/lib/watir/browser.rb:64:in `new'
>         from DivsTest.rb:3:in `<main>'

-- 
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 Jul 15 17:45:50 2011
From: watirjira at gmail.com (Michael M (JIRA))
Date: Fri, 15 Jul 2011 16:45:50 -0500 (CDT)
Subject: [Wtr-development] [JIRA] Commented: (WTR-485) Waitr fails to
 fire_event for select_list
In-Reply-To: <14447967.3.1310140430263.JavaMail.oqa-j2ee@openqa01.managed.contegix.com>
Message-ID: <24790677.46.1310766350538.JavaMail.oqa-j2ee@openqa01.managed.contegix.com>


    [ http://jira.openqa.org/browse/WTR-485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20236#action_20236 ] 

Michael M commented on WTR-485:
-------------------------------

Curious if anyone has any idea how to work-a-round this. We have some selects that have JS triggers on them to show/hide other parts of the page depending on what type of object they are adding. Right now when the select is changed, we have no way of forcing the event to fire.

What would be even better is if Watir automatically fires all the events that would typically be fired when a user changes a single-select list (as watir-webdriver does).

> Waitr fails to fire_event for select_list
> -----------------------------------------
>
>                 Key: WTR-485
>                 URL: http://jira.openqa.org/browse/WTR-485
>             Project: Watir
>          Issue Type: Bug
>          Components: Inputs
>    Affects Versions: 1.8.0
>         Environment: Windows XP SP3 (64-bit), Internet Explorer 8.0.6001.18702 (32-bit)
>            Reporter: Michael M
>            Priority: Major
>
> Watir is able to fire an event for a select list if there are events 
> of the required type registered to the element. If, however, there are 
> no objects registered via JavaScript to the select element, then it 
> fails.
> Versions: 
> Ruby 1.9.2p180 
> Watir 1.9.1.rc1
> HTML Code Sample: 
> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http:// 
> www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> 
> <html xmlns="http://www.w3.org/1999/xhtml"> 
>   <head> 
>     <title>fire event sample</title> 
>  </head> 
>   <body> 
>     <select name="select"> 
>       <option value="1">value1</option> 
>       <option value="2">value2</option> 
>     </select> 
>   </body> 
> </html>
> Ruby Code Sample: 
> require 'watir' 
> browser = Watir::Browser.new 
> browser.goto "http://<path.to>/testPage.html" 
> browser.select_list(:name, 'select').fire_event('change')
> Expected Result: 
> Code should execute without any errors, firing events if there were
> any, and otherwise doing nothing (just like the equivalent behaviour
> in JavaScript).
> Actual Result:
> C:/Ruby192/lib/ruby/gems/1.9.1/gems/watir-1.9.1.rc1/lib/watir/
> element.rb:339:in `method_missing': (in OLE method `fireEvent': )
> (WIN32OLERuntimeError) 
>     OLE error code:80070057 in htmlfile 
>       Invalid argument. 
>     HRESULT error code:0x80020009 
>       Exception occurred. 
>         from C:/Ruby192/lib/ruby/gems/1.9.1/gems/watir-1.9.1.rc1/lib/ 
> watir/element.rb:339:in `dispatch_event' 
>         from C:/Ruby192/lib/ruby/gems/1.9.1/gems/watir-1.9.1.rc1/lib/ 
> watir/element.rb:325:in `fire_event' 
>         from IE8FireEventBug.rb:21:in `<main>' 

-- 
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 jarmo.p at gmail.com  Sat Jul 16 12:33:42 2011
From: jarmo.p at gmail.com (Jarmo)
Date: Sat, 16 Jul 2011 19:33:42 +0300
Subject: [Wtr-development] Including Watir-WebDriver into Watir?
In-Reply-To: <CAC1iRBzUi42rEv2YXPaPKgxju78an3sb4bfMpwHBomPCGAsrhg@mail.gmail.com>
References: <CAC1iRBzUi42rEv2YXPaPKgxju78an3sb4bfMpwHBomPCGAsrhg@mail.gmail.com>
Message-ID: <CAHZHd6XOtSceep36egEJO8NuzJUQCQODz7cKAvXvPQykhZeQoA@mail.gmail.com>

It's not too ambitious. My gem, WatirSplash [1], is doing something
like that already. It is possible to switch between Watir, FireWatir
and Watir-Webdriver's different browser drivers. As a matter of fact i
started doing some work recently on Watir's Locators (e.g. they all
should support hash syntax and use as much common code as possible).
I'm gonna look probably into zero-based indexing too. Maybe i'm going
to use Bret's work, maybe not. Depends of the result of the
refactoring itself.

I think that Watir-IE needs to pass watirspec specs to become part of
Watir-WebDriver. If i'm not mistaken then there's a very long road to
go.

This brings us to another topic - What about FireWatir? Since jssh is
not compiled for newer versions of FireWatir then it seems to me that
there's no point of releasing new versions of FireWatir too, since it
is going to be quite deprecated already. What do you guys think about
that? Do you see any future for FireWatir?

[1] https://github.com/jarmo/watirsplash

On Fri, Jul 15, 2011 at 4:28 AM, Alister Scott <alister.scott at gmail.com> wrote:
> Hi,
>
> What would be needed to get to a point where Watir-Webdriver was fully
> included in Watir?
>
> Watir would choose the best driver for the platform and browser. For
> example, on Windows and IE, this would be the native Watir driver, on
> Mac-Chrome, this would be ChromeDriver.
>
> I understand the biggest difference is the zero based indexing, but I don't
> think there has been any work since October last year on this:
> https://github.com/bret/watir/tree/zero-index
>
> What I would love to see one gem "watir" that provides all the necessary
> drivers easily configurable for all platforms. We could then have unified
> documentation on watir.com that easily shows how to use this.
>
> Am I being too ambitious? What needs to be done?
>
> Cheers,
> Alister
>
> Alister Scott
> Brisbane, Australia
> Watir Web Master: http://watir.com
> Blog: http://watirmelon.com
> LinkedIn: http://www.linkedin.com/in/alisterscott
>
> "There are two ways to get enough: One is to continue to accumulate more and
> more. The other is to desire less." ~ G. K. Chesterton
>
> _______________________________________________
> Wtr-development mailing list
> Wtr-development at rubyforge.org
> http://rubyforge.org/mailman/listinfo/wtr-development
>

From watirjira at gmail.com  Sat Jul 16 12:47:50 2011
From: watirjira at gmail.com (Jarmo Pertman (JIRA))
Date: Sat, 16 Jul 2011 11:47:50 -0500 (CDT)
Subject: [Wtr-development] [JIRA] Commented: (WTR-485) Waitr fails to
 fire_event for select_list
In-Reply-To: <14447967.3.1310140430263.JavaMail.oqa-j2ee@openqa01.managed.contegix.com>
Message-ID: <20102909.50.1310834870472.JavaMail.oqa-j2ee@openqa01.managed.contegix.com>


    [ http://jira.openqa.org/browse/WTR-485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20237#action_20237 ] 

Jarmo Pertman commented on WTR-485:
-----------------------------------

The problem is that you're trying to fire a non-existing event - "change". The correct event would be "onchange". I modified your html to have an onChange handler registerd to it:
<select name="select" onchange="alert(1)"> 

Now if you select other value, you will get an JavaScript alert window, try it out manually.

Now, this triggers the window too:
b.select_list(:name, 'select').fire_event('onchange')

And if you select the value:
b.select_list(:name, 'select').select('value2')

So, as a matter of fact, it does trigger the "onChange" event automatically too. If you have some other custom events binded to that select then they won't be triggered of course and you'd have to fire them manually. If you cannot fire then with #fire_event, then try #execute_script and use the JavaScript framework which is used on the page like jQuery, Prototype or some other.

May i close this issue now or are you still having problems?

> Waitr fails to fire_event for select_list
> -----------------------------------------
>
>                 Key: WTR-485
>                 URL: http://jira.openqa.org/browse/WTR-485
>             Project: Watir
>          Issue Type: Bug
>          Components: Inputs
>    Affects Versions: 1.8.0
>         Environment: Windows XP SP3 (64-bit), Internet Explorer 8.0.6001.18702 (32-bit)
>            Reporter: Michael M
>            Priority: Major
>
> Watir is able to fire an event for a select list if there are events 
> of the required type registered to the element. If, however, there are 
> no objects registered via JavaScript to the select element, then it 
> fails.
> Versions: 
> Ruby 1.9.2p180 
> Watir 1.9.1.rc1
> HTML Code Sample: 
> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http:// 
> www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> 
> <html xmlns="http://www.w3.org/1999/xhtml"> 
>   <head> 
>     <title>fire event sample</title> 
>  </head> 
>   <body> 
>     <select name="select"> 
>       <option value="1">value1</option> 
>       <option value="2">value2</option> 
>     </select> 
>   </body> 
> </html>
> Ruby Code Sample: 
> require 'watir' 
> browser = Watir::Browser.new 
> browser.goto "http://<path.to>/testPage.html" 
> browser.select_list(:name, 'select').fire_event('change')
> Expected Result: 
> Code should execute without any errors, firing events if there were
> any, and otherwise doing nothing (just like the equivalent behaviour
> in JavaScript).
> Actual Result:
> C:/Ruby192/lib/ruby/gems/1.9.1/gems/watir-1.9.1.rc1/lib/watir/
> element.rb:339:in `method_missing': (in OLE method `fireEvent': )
> (WIN32OLERuntimeError) 
>     OLE error code:80070057 in htmlfile 
>       Invalid argument. 
>     HRESULT error code:0x80020009 
>       Exception occurred. 
>         from C:/Ruby192/lib/ruby/gems/1.9.1/gems/watir-1.9.1.rc1/lib/ 
> watir/element.rb:339:in `dispatch_event' 
>         from C:/Ruby192/lib/ruby/gems/1.9.1/gems/watir-1.9.1.rc1/lib/ 
> watir/element.rb:325:in `fire_event' 
>         from IE8FireEventBug.rb:21:in `<main>' 

-- 
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 Jul 17 12:42:51 2011
From: watirjira at gmail.com (Venugopal S Shenoy (JIRA))
Date: Sun, 17 Jul 2011 11:42:51 -0500 (CDT)
Subject: [Wtr-development] [JIRA] Commented: (WTR-481) Not able to open new
 IE after it is closed.
In-Reply-To: <31083542.38.1307636456038.JavaMail.oqa-j2ee@openqa01.managed.contegix.com>
Message-ID: <18929902.54.1310920971224.JavaMail.oqa-j2ee@openqa01.managed.contegix.com>


    [ http://jira.openqa.org/browse/WTR-481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20238#action_20238 ] 

Venugopal S Shenoy commented on WTR-481:
----------------------------------------

Is this critical bug be resolved soon?
It is still unassigned...

> Not able to open new IE after it is closed.
> -------------------------------------------
>
>                 Key: WTR-481
>                 URL: http://jira.openqa.org/browse/WTR-481
>             Project: Watir
>          Issue Type: Bug
>          Components: Unit Tests
>    Affects Versions: Soon
>         Environment: Windows XP running IE7
>            Reporter: bhavesh
>            Priority: Critical
>             Fix For: Soon
>
>
> Hi, 
> I have to close IE and open new IE  again in every testcase. 
> I written an routine like this : 
>   def setupnew(current_component="") 
>         $ie.close if $ie 
>         sleep(10) 
>         $ie = Watir::IE.new() 
>         sleep(10) 
>         case current_component 
>                   when "WEB_ADMIN" 
>                           $ie.goto($adminLink) 
>                   when "WEB_REPORT" 
>                           $ie.goto($reportLink) 
>                   when "WEB_SEARCH" 
>                           $ie.goto($searchLink) 
>                   else 
>                           #puts "Setup case does not match" 
>         end 
>   end 
> This works well in Ruby 1.8 
> Recently i upgrade to Ruby 1.9.2 and this routine start failing. 
> It closes the IE if it is open but then not opening the new IE  it 
> just came out of script throwing error. 
> Error coming out as : 
>     TestCaseNum: I18N_0001 
>     Description: Add AD Authentication  from Webadmin, for FIGS. 
> E 
> Finished in 0.468750 seconds. 
>   1) Error: 
> test_0001(TC_I18N): 
> NoMethodError: unknown property or method: `name' 
>     HRESULT error code:0x800706ba 
>       The RPC server is unavailable. 
>     C:/Ruby192/lib/ruby/gems/1.9.1/gems/watir-1.8.1/lib/watir/ie- 
> class.rb:319:in 
>  `method_missing' 
>     C:/Ruby192/lib/ruby/gems/1.9.1/gems/watir-1.8.1/lib/watir/ie- 
> class.rb:319:in 
>  `exists?' 
>     C:/Ruby192/lib/ruby/gems/1.9.1/gems/watir-1.8.1/lib/watir/ie- 
> class.rb:406:in 
>  `close' 
>     C:/IE_AUTOMATION/kazeon/qa/watir-v1_4-TIP/KazModules/I18N/ 
> I18N_Regression.rb 
> :47:in `setupnew' 
>     C:/IE_AUTOMATION/kazeon/qa/watir-v1_4-TIP/KazModules/I18N/ 
> I18N_Regression.rb 
> :102:in `test_0001' 
>  got the problem but not the solution. 
> In watir 1.6.7 which i use previously, code for ie.close is like 
> this : 
> #C:\ruby\lib\ruby\gems\1.8\gems\watir-1.6.7\lib\watir 
>     # Closes the Browser 
>     def close 
>       return unless exists? 
>       @closing = true 
>       @ie.stop 
>       wait rescue nil 
>       chwnd = @ie.hwnd.to_i 
>       @ie.quit 
>       while Win32API.new("user32","IsWindow", 'L', 'L').Call(chwnd) == 
> 1 
>         sleep 0.3 
>       end 
>     end 
> In watir 1.8.1 which i use now, code for ie.close is like this : 
> C:\Ruby192\lib\ruby\gems\1.9.1\gems\watir-1.8.1\lib\watir 
>     # Closes the Browser 
>     def close 
>       return unless exists? 
>       @ie.stop 
>       wait rescue nil 
>       chwnd = @ie.hwnd.to_i 
>       @ie.quit 
>       t = Time.now 
>       while exists? 
>         # just in case to avoid possible endless loop if failing to 
> close some 
>         # window or tab 
>         break if Time.now - t > 10 
>         sleep 0.3 
>       end 
>     end 
> There is an change in code in 1.8.1. 
> If i replace the piece of code for ie.close of version 1.6.7  in 1.8.1 
> file, the same routine starts working fine. 
> So what needs to be done now to have this working with 1.8.1 code? 
> Bhavesh 

-- 
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  Mon Jul 18 06:11:12 2011
From: zeljko.filipin at wa-research.ch (=?UTF-8?Q?=C5=BDeljko_Filipin?=)
Date: Mon, 18 Jul 2011 12:11:12 +0200
Subject: [Wtr-development] Including Watir-WebDriver into Watir?
In-Reply-To: <CAHZHd6XOtSceep36egEJO8NuzJUQCQODz7cKAvXvPQykhZeQoA@mail.gmail.com>
References: <CAC1iRBzUi42rEv2YXPaPKgxju78an3sb4bfMpwHBomPCGAsrhg@mail.gmail.com>
	<CAHZHd6XOtSceep36egEJO8NuzJUQCQODz7cKAvXvPQykhZeQoA@mail.gmail.com>
Message-ID: <CABfBeAr0r=Rd8T5o55Y1aff8ip6A4n9j7cGJ8PUND=q38e59LQ@mail.gmail.com>

On Sat, Jul 16, 2011 at 6:33 PM, Jarmo <jarmo.p at gmail.com> wrote:
> Do you see any future for FireWatir?

No.

?eljko
--
watir.com - community manager
watir.com/book - author
watirpodcast.com - host
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/wtr-development/attachments/20110718/b550e142/attachment.html>

From watirjira at gmail.com  Mon Jul 18 16:19:52 2011
From: watirjira at gmail.com (Bret Pettichord (JIRA))
Date: Mon, 18 Jul 2011 15:19:52 -0500 (CDT)
Subject: [Wtr-development] [JIRA] Commented: (WTR-481) Not able to open new
 IE after it is closed.
In-Reply-To: <31083542.38.1307636456038.JavaMail.oqa-j2ee@openqa01.managed.contegix.com>
Message-ID: <19081769.60.1311020392193.JavaMail.oqa-j2ee@openqa01.managed.contegix.com>


    [ http://jira.openqa.org/browse/WTR-481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20239#action_20239 ] 

Bret Pettichord commented on WTR-481:
-------------------------------------

Yes I think we saw a fix for this recently.

> Not able to open new IE after it is closed.
> -------------------------------------------
>
>                 Key: WTR-481
>                 URL: http://jira.openqa.org/browse/WTR-481
>             Project: Watir
>          Issue Type: Bug
>          Components: Unit Tests
>    Affects Versions: Soon
>         Environment: Windows XP running IE7
>            Reporter: bhavesh
>            Priority: Critical
>             Fix For: Soon
>
>
> Hi, 
> I have to close IE and open new IE  again in every testcase. 
> I written an routine like this : 
>   def setupnew(current_component="") 
>         $ie.close if $ie 
>         sleep(10) 
>         $ie = Watir::IE.new() 
>         sleep(10) 
>         case current_component 
>                   when "WEB_ADMIN" 
>                           $ie.goto($adminLink) 
>                   when "WEB_REPORT" 
>                           $ie.goto($reportLink) 
>                   when "WEB_SEARCH" 
>                           $ie.goto($searchLink) 
>                   else 
>                           #puts "Setup case does not match" 
>         end 
>   end 
> This works well in Ruby 1.8 
> Recently i upgrade to Ruby 1.9.2 and this routine start failing. 
> It closes the IE if it is open but then not opening the new IE  it 
> just came out of script throwing error. 
> Error coming out as : 
>     TestCaseNum: I18N_0001 
>     Description: Add AD Authentication  from Webadmin, for FIGS. 
> E 
> Finished in 0.468750 seconds. 
>   1) Error: 
> test_0001(TC_I18N): 
> NoMethodError: unknown property or method: `name' 
>     HRESULT error code:0x800706ba 
>       The RPC server is unavailable. 
>     C:/Ruby192/lib/ruby/gems/1.9.1/gems/watir-1.8.1/lib/watir/ie- 
> class.rb:319:in 
>  `method_missing' 
>     C:/Ruby192/lib/ruby/gems/1.9.1/gems/watir-1.8.1/lib/watir/ie- 
> class.rb:319:in 
>  `exists?' 
>     C:/Ruby192/lib/ruby/gems/1.9.1/gems/watir-1.8.1/lib/watir/ie- 
> class.rb:406:in 
>  `close' 
>     C:/IE_AUTOMATION/kazeon/qa/watir-v1_4-TIP/KazModules/I18N/ 
> I18N_Regression.rb 
> :47:in `setupnew' 
>     C:/IE_AUTOMATION/kazeon/qa/watir-v1_4-TIP/KazModules/I18N/ 
> I18N_Regression.rb 
> :102:in `test_0001' 
>  got the problem but not the solution. 
> In watir 1.6.7 which i use previously, code for ie.close is like 
> this : 
> #C:\ruby\lib\ruby\gems\1.8\gems\watir-1.6.7\lib\watir 
>     # Closes the Browser 
>     def close 
>       return unless exists? 
>       @closing = true 
>       @ie.stop 
>       wait rescue nil 
>       chwnd = @ie.hwnd.to_i 
>       @ie.quit 
>       while Win32API.new("user32","IsWindow", 'L', 'L').Call(chwnd) == 
> 1 
>         sleep 0.3 
>       end 
>     end 
> In watir 1.8.1 which i use now, code for ie.close is like this : 
> C:\Ruby192\lib\ruby\gems\1.9.1\gems\watir-1.8.1\lib\watir 
>     # Closes the Browser 
>     def close 
>       return unless exists? 
>       @ie.stop 
>       wait rescue nil 
>       chwnd = @ie.hwnd.to_i 
>       @ie.quit 
>       t = Time.now 
>       while exists? 
>         # just in case to avoid possible endless loop if failing to 
> close some 
>         # window or tab 
>         break if Time.now - t > 10 
>         sleep 0.3 
>       end 
>     end 
> There is an change in code in 1.8.1. 
> If i replace the piece of code for ie.close of version 1.6.7  in 1.8.1 
> file, the same routine starts working fine. 
> So what needs to be done now to have this working with 1.8.1 code? 
> Bhavesh 

-- 
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 Jul 18 17:00:51 2011
From: watirjira at gmail.com (Jarmo Pertman (JIRA))
Date: Mon, 18 Jul 2011 16:00:51 -0500 (CDT)
Subject: [Wtr-development] [JIRA] Commented: (WTR-481) Not able to open new
 IE after it is closed.
In-Reply-To: <31083542.38.1307636456038.JavaMail.oqa-j2ee@openqa01.managed.contegix.com>
Message-ID: <30498151.62.1311022851223.JavaMail.oqa-j2ee@openqa01.managed.contegix.com>


    [ http://jira.openqa.org/browse/WTR-481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20240#action_20240 ] 

Jarmo Pertman commented on WTR-481:
-----------------------------------

nope, it was something else - this is in my todo list and i'll fix it soon

> Not able to open new IE after it is closed.
> -------------------------------------------
>
>                 Key: WTR-481
>                 URL: http://jira.openqa.org/browse/WTR-481
>             Project: Watir
>          Issue Type: Bug
>          Components: Unit Tests
>    Affects Versions: Soon
>         Environment: Windows XP running IE7
>            Reporter: bhavesh
>            Priority: Critical
>             Fix For: Soon
>
>
> Hi, 
> I have to close IE and open new IE  again in every testcase. 
> I written an routine like this : 
>   def setupnew(current_component="") 
>         $ie.close if $ie 
>         sleep(10) 
>         $ie = Watir::IE.new() 
>         sleep(10) 
>         case current_component 
>                   when "WEB_ADMIN" 
>                           $ie.goto($adminLink) 
>                   when "WEB_REPORT" 
>                           $ie.goto($reportLink) 
>                   when "WEB_SEARCH" 
>                           $ie.goto($searchLink) 
>                   else 
>                           #puts "Setup case does not match" 
>         end 
>   end 
> This works well in Ruby 1.8 
> Recently i upgrade to Ruby 1.9.2 and this routine start failing. 
> It closes the IE if it is open but then not opening the new IE  it 
> just came out of script throwing error. 
> Error coming out as : 
>     TestCaseNum: I18N_0001 
>     Description: Add AD Authentication  from Webadmin, for FIGS. 
> E 
> Finished in 0.468750 seconds. 
>   1) Error: 
> test_0001(TC_I18N): 
> NoMethodError: unknown property or method: `name' 
>     HRESULT error code:0x800706ba 
>       The RPC server is unavailable. 
>     C:/Ruby192/lib/ruby/gems/1.9.1/gems/watir-1.8.1/lib/watir/ie- 
> class.rb:319:in 
>  `method_missing' 
>     C:/Ruby192/lib/ruby/gems/1.9.1/gems/watir-1.8.1/lib/watir/ie- 
> class.rb:319:in 
>  `exists?' 
>     C:/Ruby192/lib/ruby/gems/1.9.1/gems/watir-1.8.1/lib/watir/ie- 
> class.rb:406:in 
>  `close' 
>     C:/IE_AUTOMATION/kazeon/qa/watir-v1_4-TIP/KazModules/I18N/ 
> I18N_Regression.rb 
> :47:in `setupnew' 
>     C:/IE_AUTOMATION/kazeon/qa/watir-v1_4-TIP/KazModules/I18N/ 
> I18N_Regression.rb 
> :102:in `test_0001' 
>  got the problem but not the solution. 
> In watir 1.6.7 which i use previously, code for ie.close is like 
> this : 
> #C:\ruby\lib\ruby\gems\1.8\gems\watir-1.6.7\lib\watir 
>     # Closes the Browser 
>     def close 
>       return unless exists? 
>       @closing = true 
>       @ie.stop 
>       wait rescue nil 
>       chwnd = @ie.hwnd.to_i 
>       @ie.quit 
>       while Win32API.new("user32","IsWindow", 'L', 'L').Call(chwnd) == 
> 1 
>         sleep 0.3 
>       end 
>     end 
> In watir 1.8.1 which i use now, code for ie.close is like this : 
> C:\Ruby192\lib\ruby\gems\1.9.1\gems\watir-1.8.1\lib\watir 
>     # Closes the Browser 
>     def close 
>       return unless exists? 
>       @ie.stop 
>       wait rescue nil 
>       chwnd = @ie.hwnd.to_i 
>       @ie.quit 
>       t = Time.now 
>       while exists? 
>         # just in case to avoid possible endless loop if failing to 
> close some 
>         # window or tab 
>         break if Time.now - t > 10 
>         sleep 0.3 
>       end 
>     end 
> There is an change in code in 1.8.1. 
> If i replace the piece of code for ie.close of version 1.6.7  in 1.8.1 
> file, the same routine starts working fine. 
> So what needs to be done now to have this working with 1.8.1 code? 
> Bhavesh 

-- 
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 alister.scott at gmail.com  Mon Jul 18 20:30:41 2011
From: alister.scott at gmail.com (Alister Scott)
Date: Tue, 19 Jul 2011 10:30:41 +1000
Subject: [Wtr-development] Including Watir-WebDriver into Watir?
In-Reply-To: <CABfBeAr0r=Rd8T5o55Y1aff8ip6A4n9j7cGJ8PUND=q38e59LQ@mail.gmail.com>
References: <CAC1iRBzUi42rEv2YXPaPKgxju78an3sb4bfMpwHBomPCGAsrhg@mail.gmail.com>
	<CAHZHd6XOtSceep36egEJO8NuzJUQCQODz7cKAvXvPQykhZeQoA@mail.gmail.com>
	<CABfBeAr0r=Rd8T5o55Y1aff8ip6A4n9j7cGJ8PUND=q38e59LQ@mail.gmail.com>
Message-ID: <CAC1iRByF4qKNnqbSRo16sOg_BP9heMXRDK01tmYXzz5OON3QYQ@mail.gmail.com>

I think FireWatir should be end-of-life'd, but until watir can offer an
alternative, such as use watir-webdriver, I am reluctant to announce it.

Cheers,

Alister

On Mon, Jul 18, 2011 at 8:11 PM, ?eljko Filipin <
zeljko.filipin at wa-research.ch> wrote:

> On Sat, Jul 16, 2011 at 6:33 PM, Jarmo <jarmo.p at gmail.com> wrote:
> > Do you see any future for FireWatir?
>
> No.
>
> ?eljko
> --
> watir.com - community manager
> watir.com/book - author
> watirpodcast.com - host
>
> _______________________________________________
> Wtr-development mailing list
> Wtr-development at rubyforge.org
> http://rubyforge.org/mailman/listinfo/wtr-development
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/wtr-development/attachments/20110719/242dbda1/attachment-0001.html>

From jarmo.p at gmail.com  Sun Jul 24 17:53:09 2011
From: jarmo.p at gmail.com (Jarmo)
Date: Mon, 25 Jul 2011 00:53:09 +0300
Subject: [Wtr-development] Watir 2.0.0.rc2 released
Message-ID: <CAHZHd6XmJgCBPJob6YkVPcemcphEgTxDTAdZMmc_AZaqu+u4Sg@mail.gmail.com>

Good news everyone!

I've found some time to play with Watir and managed to release a new version
- 2.0.0.rc2 (rc1 had buggy dependency, sorry)!

There are some big changes including 0-based-indexing, which is enabled by
default and not releasing new versions of FireWatir.
Also, all collection factory methods accept now (multiple)
specifiers/locators. A lot of these changes are compatible with
Watir-WebDriver (see the list of incompatibilities compared with previous
versions at
https://github.com/jarib/watir-webdriver/wiki/Comparison-with-Watir-1.X).

Here is the full changelog:
* RIP FireWatir - there won't be any new releases
* all elements are using 0-based indexing instead of old 1-based indexing:
 - disable it temporarily: require "watir";
Watir.options[:zero_based_indexing] = false
* #radio and #checkbox methods doesn't allow 3 parameters anymore for
locating with "value"
 - use browser.radio(:name => "something", :value => "some value") syntax
instead for locating with "value"
* all element methods accept now multiple-specifiers with hash syntax, for
example:
 - browser.element(:class => "someclass", :name => "somename")
* all elements are searchable by :xpath and :css now (note that it's usually
slower than searching by other specifiers)
* #button, #form and #frame doesn't accept single string as a specifier
anymore to search by name:
 - use browser.frame(:name => "name") or browser.frame(:name, "name") syntax
instead
* :index => 0 is used as a default specifier if nothing is specified:
 - browser.div(:id => "id").table.tr is same as browser.div(:id =>
"id").table(:index => 0).tr(:index => 0)
* all collection methods accept now specifiers too:
 - browser.divs(:class => "someclass").each {|div| puts div.class_name} # =>
"someclass"
* removed FormElement class
* renamed CheckBox class to Checkbox
* renamed CheckBoxes class to Checkboxes
* added aliases:
 - tr => row
 - trs => rows
 - td => cell
 - tds => cells
 - a => link
 - as => links

You can try these changes out by executing `gem install watir --pre`!

Since this release includes quite many core changes (even non-visible ones)
then i really encourage everyone to run their current tests against this
version first by disabling 0-based-indexing. Let me know about the things
which did get broken after the upgrade. Hope there's none :)

Cheers!

Jarmo Pertman
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/wtr-development/attachments/20110725/d67a96cf/attachment.html>

From zeljko.filipin at wa-research.ch  Mon Jul 25 06:23:39 2011
From: zeljko.filipin at wa-research.ch (=?UTF-8?Q?=C5=BDeljko_Filipin?=)
Date: Mon, 25 Jul 2011 12:23:39 +0200
Subject: [Wtr-development] [wtr-general] Watir 2.0.0.rc2 released
In-Reply-To: <CAHZHd6XmJgCBPJob6YkVPcemcphEgTxDTAdZMmc_AZaqu+u4Sg@mail.gmail.com>
References: <CAHZHd6XmJgCBPJob6YkVPcemcphEgTxDTAdZMmc_AZaqu+u4Sg@mail.gmail.com>
Message-ID: <CABfBeApkSatfoQu-+74901==FtB19JZGKwKFm1O06XQjL6vsug@mail.gmail.com>

On Sun, Jul 24, 2011 at 11:53 PM, Jarmo <jarmo.p at gmail.com> wrote:
> I've found some time to play with Watir and managed to release a new
version - 2.0.0.rc2 (rc1 had buggy dependency, sorry)!

Great news! Would you like to create a blog post for watir.com?

I thought the plan is to release Watir 2.0 when we integrate watir-webdriver
as firefox driver? (Also Chrome and Opera.)

?eljko
--
watir.com - community manager
watir.com/book - author
watirpodcast.com - host
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/wtr-development/attachments/20110725/8f72595b/attachment.html>

From jari.bakken at gmail.com  Mon Jul 25 07:01:07 2011
From: jari.bakken at gmail.com (Jari Bakken)
Date: Mon, 25 Jul 2011 13:01:07 +0200
Subject: [Wtr-development] Including Watir-WebDriver into Watir?
In-Reply-To: <CAPjkWY1gKsVPP0Sz9RtKE2JV=Ey9yq==hNW-JU8iDuNRdn-cUA@mail.gmail.com>
References: <CAC1iRBzUi42rEv2YXPaPKgxju78an3sb4bfMpwHBomPCGAsrhg@mail.gmail.com>
	<CAPjkWY1gKsVPP0Sz9RtKE2JV=Ey9yq==hNW-JU8iDuNRdn-cUA@mail.gmail.com>
Message-ID: <CAEMjNnLoCchvYp+MjyBpfYbks+BkA=Q3PLjEmpCkWviN=Ab_Sg@mail.gmail.com>

On Fri, Jul 15, 2011 at 11:11 PM, Bret Pettichord <bret at pettichord.com> wrote:
>
> The big issue the remains open is the ownership and interface for
> Watir::Browser. Watir and Watir-Webdriver have conflicting versions of this
> module/class. Watir's version (actually in common-watir) is pluggable to use
> different implementations of watir-compatable drivers. Watir-WebDriver's
> assumes you are using webdriver for all browsers. What I would like to see
> would be for Watir-Webdriver to rename its class and then update
> Watir::Browser to user Watir-Webdriver as the default implementation for
> Firefox and perhaps others.
>

So would renaming Watir::Browser to Watir::WebDriver in
watir-webdriver solve this?

From alister.scott at gmail.com  Mon Jul 25 07:59:51 2011
From: alister.scott at gmail.com (Alister Scott)
Date: Mon, 25 Jul 2011 21:59:51 +1000
Subject: [Wtr-development] [wtr-general] Watir 2.0.0.rc2 released
In-Reply-To: <CAEMjNn+mBfTbq4Y+KMoEHY8P4zSXghMJceK+Xh4tDXv-T8b7zQ@mail.gmail.com>
References: <CAHZHd6XmJgCBPJob6YkVPcemcphEgTxDTAdZMmc_AZaqu+u4Sg@mail.gmail.com>
	<CAEMjNn+mBfTbq4Y+KMoEHY8P4zSXghMJceK+Xh4tDXv-T8b7zQ@mail.gmail.com>
Message-ID: <CAC1iRBzyWoCk+R9k-UzFDJOq2vT-mzorW+S9eWooEa6U+6_5FQ@mail.gmail.com>

I am having a play around with this on Win7/Ruby 1.9.2, but can't get very
far.

What am I doing wrong?

irb(main):001:0> require 'watir'
=> true
irb(main):002:0> b = Watir::Browser.new
=> #<Watir::IE:0x..f90492b14 url="about:blank" title="">
irb(main):003:0> b.goto 'www.google.com'
=> 1.363929
irb(main):004:0> b.text_field(:name => "q").set "s"
NoMethodError: unknown property or method: `createEvent'
    HRESULT error code:0x80020006
      Unknown name.
        from
C:/Ruby192/lib/ruby/gems/1.9.1/gems/watir-2.0.0.rc2/lib/watir/element.rb:377:in
`method_missing'
        from
C:/Ruby192/lib/ruby/gems/1.9.1/gems/watir-2.0.0.rc2/lib/watir/element.rb:377:in
`create_event'
        from
C:/Ruby192/lib/ruby/gems/1.9.1/gems/watir-2.0.0.rc2/lib/watir/element.rb:343:in
`dispatch_event'
        from
C:/Ruby192/lib/ruby/gems/1.9.1/gems/watir-2.0.0.rc2/lib/watir/input_elements.rb:376:in
`set'
        from (irb):4
        from C:/Ruby192/bin/irb:12:in `<main>'
irb(main):005:0>

Cheers,

Alister Scott
Brisbane, Australia
Watir Web Master: http://watir.com
Blog: http://watirmelon.com
LinkedIn: http://www.linkedin.com/in/alisterscott

"There are two ways to get enough: One is to continue to accumulate more and
more. The other is to desire less." *~ G. K. Chesterton*


On Mon, Jul 25, 2011 at 8:59 PM, Jari Bakken <jari.bakken at gmail.com> wrote:

> On Sun, Jul 24, 2011 at 11:53 PM, Jarmo <jarmo.p at gmail.com> wrote:
> > Good news everyone!
> > I've found some time to play with Watir and managed to release a new
> version
> > - 2.0.0.rc2 (rc1 had buggy dependency, sorry)!
> > There are some big changes including 0-based-indexing, which is enabled
> by
> > default and not releasing new versions of FireWatir.
> > Also, all collection factory methods accept now (multiple)
> > specifiers/locators. A lot of these changes are compatible with
> > Watir-WebDriver (see the list of incompatibilities compared with previous
> > versions
>
> Nice work!
>
> > * renamed CheckBox class to Checkbox
> > * renamed CheckBoxes class to Checkboxes
>
> What's the rationale for this? This adds a new incompatibility with
> watir-webdriver and breaks backwards compatibility for anyone relying
> on the class name. The change seems rather arbitrary.
>
> Jari
>
> --
> Before posting, please read http://watir.com/support. In short: search
> before you ask, be nice.
>
> watir-general at googlegroups.com
> http://groups.google.com/group/watir-general
> watir-general+unsubscribe at googlegroups.com<http://groups.google.com/group/watir-general%0Awatir-general+unsubscribe at googlegroups.com>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/wtr-development/attachments/20110725/dde67cd4/attachment.html>

From jarmo.p at gmail.com  Mon Jul 25 08:03:20 2011
From: jarmo.p at gmail.com (Jarmo)
Date: Mon, 25 Jul 2011 15:03:20 +0300
Subject: [Wtr-development] [wtr-general] Watir 2.0.0.rc2 released
In-Reply-To: <CAC1iRBzyWoCk+R9k-UzFDJOq2vT-mzorW+S9eWooEa6U+6_5FQ@mail.gmail.com>
References: <CAHZHd6XmJgCBPJob6YkVPcemcphEgTxDTAdZMmc_AZaqu+u4Sg@mail.gmail.com>
	<CAEMjNn+mBfTbq4Y+KMoEHY8P4zSXghMJceK+Xh4tDXv-T8b7zQ@mail.gmail.com>
	<CAC1iRBzyWoCk+R9k-UzFDJOq2vT-mzorW+S9eWooEa6U+6_5FQ@mail.gmail.com>
Message-ID: <CAHZHd6Vf_OMRvD9ER0n2uHYpvaxqtPd4fVqd7=pT9WdJ_d-oXA@mail.gmail.com>

Don't use Ruby 1.9.2 right now since it is related with other bugs related
with 1.9.2. Didn't want to fix those at the moment to avoid even bigger
changes.

Jarmo

On Mon, Jul 25, 2011 at 2:59 PM, Alister Scott <alister.scott at gmail.com>wrote:

> I am having a play around with this on Win7/Ruby 1.9.2, but can't get very
> far.
>
> What am I doing wrong?
>
> irb(main):001:0> require 'watir'
> => true
> irb(main):002:0> b = Watir::Browser.new
> => #<Watir::IE:0x..f90492b14 url="about:blank" title="">
> irb(main):003:0> b.goto 'www.google.com'
> => 1.363929
> irb(main):004:0> b.text_field(:name => "q").set "s"
> NoMethodError: unknown property or method: `createEvent'
>     HRESULT error code:0x80020006
>       Unknown name.
>         from
> C:/Ruby192/lib/ruby/gems/1.9.1/gems/watir-2.0.0.rc2/lib/watir/element.rb:377:in
> `method_missing'
>         from
> C:/Ruby192/lib/ruby/gems/1.9.1/gems/watir-2.0.0.rc2/lib/watir/element.rb:377:in
> `create_event'
>         from
> C:/Ruby192/lib/ruby/gems/1.9.1/gems/watir-2.0.0.rc2/lib/watir/element.rb:343:in
> `dispatch_event'
>         from
> C:/Ruby192/lib/ruby/gems/1.9.1/gems/watir-2.0.0.rc2/lib/watir/input_elements.rb:376:in
> `set'
>         from (irb):4
>         from C:/Ruby192/bin/irb:12:in `<main>'
> irb(main):005:0>
>
> Cheers,
>
> Alister Scott
> Brisbane, Australia
> Watir Web Master: http://watir.com
> Blog: http://watirmelon.com
> LinkedIn: http://www.linkedin.com/in/alisterscott
>
> "There are two ways to get enough: One is to continue to accumulate more
> and more. The other is to desire less." *~ G. K. Chesterton*
>
>
> On Mon, Jul 25, 2011 at 8:59 PM, Jari Bakken <jari.bakken at gmail.com>wrote:
>
>> On Sun, Jul 24, 2011 at 11:53 PM, Jarmo <jarmo.p at gmail.com> wrote:
>> > Good news everyone!
>> > I've found some time to play with Watir and managed to release a new
>> version
>> > - 2.0.0.rc2 (rc1 had buggy dependency, sorry)!
>> > There are some big changes including 0-based-indexing, which is enabled
>> by
>> > default and not releasing new versions of FireWatir.
>> > Also, all collection factory methods accept now (multiple)
>> > specifiers/locators. A lot of these changes are compatible with
>> > Watir-WebDriver (see the list of incompatibilities compared with
>> previous
>> > versions
>>
>> Nice work!
>>
>>
>> > * renamed CheckBox class to Checkbox
>> > * renamed CheckBoxes class to Checkboxes
>>
>> What's the rationale for this? This adds a new incompatibility with
>> watir-webdriver and breaks backwards compatibility for anyone relying
>> on the class name. The change seems rather arbitrary.
>>
>> Jari
>>
>> --
>> Before posting, please read http://watir.com/support. In short: search
>> before you ask, be nice.
>>
>> watir-general at googlegroups.com
>> http://groups.google.com/group/watir-general
>> watir-general+unsubscribe at googlegroups.com<http://groups.google.com/group/watir-general%0Awatir-general+unsubscribe at googlegroups.com>
>>
>
>
> _______________________________________________
> Wtr-development mailing list
> Wtr-development at rubyforge.org
> http://rubyforge.org/mailman/listinfo/wtr-development
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/wtr-development/attachments/20110725/be956b92/attachment-0001.html>

From jarmo.p at gmail.com  Mon Jul 25 08:09:13 2011
From: jarmo.p at gmail.com (Jarmo)
Date: Mon, 25 Jul 2011 15:09:13 +0300
Subject: [Wtr-development] [wtr-general] Watir 2.0.0.rc2 released
In-Reply-To: <CABfBeApkSatfoQu-+74901==FtB19JZGKwKFm1O06XQjL6vsug@mail.gmail.com>
References: <CAHZHd6XmJgCBPJob6YkVPcemcphEgTxDTAdZMmc_AZaqu+u4Sg@mail.gmail.com>
	<CABfBeApkSatfoQu-+74901==FtB19JZGKwKFm1O06XQjL6vsug@mail.gmail.com>
Message-ID: <CAHZHd6UsWVPhv3NXSpZXLK=4P1QF0VCk_GuKzjqi-sgRi7s1cw@mail.gmail.com>

Since it had quite many core changes and i've been trying to follow semantic
versioning (http://semver.org/) then i needed to increase the major version.
Don't be so stuck with the version 2.0.

My suggestion would be to start fixing failures when running against
watirspec. If these are fixed, only then it's possible to integrate with
Watir-WebDriver firefox driver. Otherwise we'd just end up creating big
chunk of changes and then releasing with big boom after year has passed. I
wouldn't like to see that. Smaller steps are better - you can now use
(almost) the same code when using Watir or Watir-WebDriver, but there are
still a lot of issues which need to be fixed.

Jarmo

On Mon, Jul 25, 2011 at 1:23 PM, ?eljko Filipin <
zeljko.filipin at wa-research.ch> wrote:

> On Sun, Jul 24, 2011 at 11:53 PM, Jarmo <jarmo.p at gmail.com> wrote:
> > I've found some time to play with Watir and managed to release a new
> version - 2.0.0.rc2 (rc1 had buggy dependency, sorry)!
>
> Great news! Would you like to create a blog post for watir.com?
>
> I thought the plan is to release Watir 2.0 when we integrate
> watir-webdriver as firefox driver? (Also Chrome and Opera.)
>
> ?eljko
> --
> watir.com - community manager
> watir.com/book - author
> watirpodcast.com - host
>
> _______________________________________________
> Wtr-development mailing list
> Wtr-development at rubyforge.org
> http://rubyforge.org/mailman/listinfo/wtr-development
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/wtr-development/attachments/20110725/99e71b11/attachment.html>

From colinsdaddy at gmail.com  Mon Jul 25 08:29:46 2011
From: colinsdaddy at gmail.com (Hugh McGowan)
Date: Mon, 25 Jul 2011 07:29:46 -0500
Subject: [Wtr-development] [wtr-general] Watir 2.0.0.rc2 released
In-Reply-To: <CAHZHd6UsWVPhv3NXSpZXLK=4P1QF0VCk_GuKzjqi-sgRi7s1cw@mail.gmail.com>
References: <CAHZHd6XmJgCBPJob6YkVPcemcphEgTxDTAdZMmc_AZaqu+u4Sg@mail.gmail.com>
	<CABfBeApkSatfoQu-+74901==FtB19JZGKwKFm1O06XQjL6vsug@mail.gmail.com>
	<CAHZHd6UsWVPhv3NXSpZXLK=4P1QF0VCk_GuKzjqi-sgRi7s1cw@mail.gmail.com>
Message-ID: <CAH59Z1yAe-bEZGJFXAEpbzfQVY8OLNqKaCXPOR+eSc6PywNDjw@mail.gmail.com>

> Since it had quite many core changes and i've been trying to follow
semantic versioning (http://semver.org/) then i needed to increase the major
version. Don't be so stuck with the version 2.0.

+1 - With the zero-based indexing changes (especially changing the default)
we want to make sure it's obvious there's an API change.

Nice work, Jarmo! I'll take a look at Win7/1.8.7/IE9 and let you know if I
run into any issues.

Thanks!
Hugh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/wtr-development/attachments/20110725/b075ca18/attachment.html>

From jarmo.p at gmail.com  Mon Jul 25 10:28:19 2011
From: jarmo.p at gmail.com (Jarmo)
Date: Mon, 25 Jul 2011 17:28:19 +0300
Subject: [Wtr-development] Including Watir-WebDriver into Watir?
In-Reply-To: <CAEMjNnLoCchvYp+MjyBpfYbks+BkA=Q3PLjEmpCkWviN=Ab_Sg@mail.gmail.com>
References: <CAC1iRBzUi42rEv2YXPaPKgxju78an3sb4bfMpwHBomPCGAsrhg@mail.gmail.com>
	<CAPjkWY1gKsVPP0Sz9RtKE2JV=Ey9yq==hNW-JU8iDuNRdn-cUA@mail.gmail.com>
	<CAEMjNnLoCchvYp+MjyBpfYbks+BkA=Q3PLjEmpCkWviN=Ab_Sg@mail.gmail.com>
Message-ID: <CAHZHd6VdTxPJ+NDvPkMBEgXkMFFhr+jUQwJxnYJRt4bChWSTqQ@mail.gmail.com>

My suggestion would not to deal with that issue currently until watirspec
specs are not passing. ~30% are still failing.

Jarmo

On Mon, Jul 25, 2011 at 2:01 PM, Jari Bakken <jari.bakken at gmail.com> wrote:

> On Fri, Jul 15, 2011 at 11:11 PM, Bret Pettichord <bret at pettichord.com>
> wrote:
> >
> > The big issue the remains open is the ownership and interface for
> > Watir::Browser. Watir and Watir-Webdriver have conflicting versions of
> this
> > module/class. Watir's version (actually in common-watir) is pluggable to
> use
> > different implementations of watir-compatable drivers. Watir-WebDriver's
> > assumes you are using webdriver for all browsers. What I would like to
> see
> > would be for Watir-Webdriver to rename its class and then update
> > Watir::Browser to user Watir-Webdriver as the default implementation for
> > Firefox and perhaps others.
> >
>
> So would renaming Watir::Browser to Watir::WebDriver in
> watir-webdriver solve this?
> _______________________________________________
> Wtr-development mailing list
> Wtr-development at rubyforge.org
> http://rubyforge.org/mailman/listinfo/wtr-development
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/wtr-development/attachments/20110725/61914db3/attachment.html>

From bret at pettichord.com  Mon Jul 25 13:02:14 2011
From: bret at pettichord.com (Bret Pettichord)
Date: Mon, 25 Jul 2011 12:02:14 -0500
Subject: [Wtr-development] Watir 2.0.0.rc2 released
In-Reply-To: <CAHZHd6XmJgCBPJob6YkVPcemcphEgTxDTAdZMmc_AZaqu+u4Sg@mail.gmail.com>
References: <CAHZHd6XmJgCBPJob6YkVPcemcphEgTxDTAdZMmc_AZaqu+u4Sg@mail.gmail.com>
Message-ID: <CAPjkWY3N-VzPnEc0gTycPz_6LSidLrqj_Jash75_-JPoG9uo2Q@mail.gmail.com>

This is so exciting!

On Sun, Jul 24, 2011 at 4:53 PM, Jarmo <jarmo.p at gmail.com> wrote:

> Good news everyone!
>
> I've found some time to play with Watir and managed to release a new
> version - 2.0.0.rc2 (rc1 had buggy dependency, sorry)!
>
> There are some big changes including 0-based-indexing, which is enabled by
> default and not releasing new versions of FireWatir.
> Also, all collection factory methods accept now (multiple)
> specifiers/locators. A lot of these changes are compatible with
> Watir-WebDriver (see the list of incompatibilities compared with previous
> versions at
> https://github.com/jarib/watir-webdriver/wiki/Comparison-with-Watir-1.X).
>
> Here is the full changelog:
> * RIP FireWatir - there won't be any new releases
> * all elements are using 0-based indexing instead of old 1-based indexing:
>  - disable it temporarily: require "watir";
> Watir.options[:zero_based_indexing] = false
> * #radio and #checkbox methods doesn't allow 3 parameters anymore for
> locating with "value"
>  - use browser.radio(:name => "something", :value => "some value") syntax
> instead for locating with "value"
> * all element methods accept now multiple-specifiers with hash syntax, for
> example:
>  - browser.element(:class => "someclass", :name => "somename")
> * all elements are searchable by :xpath and :css now (note that it's
> usually slower than searching by other specifiers)
> * #button, #form and #frame doesn't accept single string as a specifier
> anymore to search by name:
>  - use browser.frame(:name => "name") or browser.frame(:name, "name")
> syntax instead
> * :index => 0 is used as a default specifier if nothing is specified:
>  - browser.div(:id => "id").table.tr is same as browser.div(:id =>
> "id").table(:index => 0).tr(:index => 0)
> * all collection methods accept now specifiers too:
>  - browser.divs(:class => "someclass").each {|div| puts div.class_name} #
> => "someclass"
> * removed FormElement class
> * renamed CheckBox class to Checkbox
> * renamed CheckBoxes class to Checkboxes
> * added aliases:
>  - tr => row
>  - trs => rows
>  - td => cell
>  - tds => cells
>  - a => link
>  - as => links
>
> You can try these changes out by executing `gem install watir --pre`!
>
> Since this release includes quite many core changes (even non-visible ones)
> then i really encourage everyone to run their current tests against this
> version first by disabling 0-based-indexing. Let me know about the things
> which did get broken after the upgrade. Hope there's none :)
>
> Cheers!
>
> Jarmo Pertman
>
> _______________________________________________
> Wtr-development mailing list
> Wtr-development at rubyforge.org
> http://rubyforge.org/mailman/listinfo/wtr-development
>



-- 
Bret Pettichord
Director, Watir Project, www.watir.com

Blog, www.testingwithvision.com
Twitter, www.twitter.com/bpettichord
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/wtr-development/attachments/20110725/c352aa11/attachment.html>

From bret at pettichord.com  Mon Jul 25 13:03:58 2011
From: bret at pettichord.com (Bret Pettichord)
Date: Mon, 25 Jul 2011 12:03:58 -0500
Subject: [Wtr-development] Including Watir-WebDriver into Watir?
In-Reply-To: <CAEMjNnLoCchvYp+MjyBpfYbks+BkA=Q3PLjEmpCkWviN=Ab_Sg@mail.gmail.com>
References: <CAC1iRBzUi42rEv2YXPaPKgxju78an3sb4bfMpwHBomPCGAsrhg@mail.gmail.com>
	<CAPjkWY1gKsVPP0Sz9RtKE2JV=Ey9yq==hNW-JU8iDuNRdn-cUA@mail.gmail.com>
	<CAEMjNnLoCchvYp+MjyBpfYbks+BkA=Q3PLjEmpCkWviN=Ab_Sg@mail.gmail.com>
Message-ID: <CAPjkWY3mLCMweUJc9q7KAN2yfStuofgmUq5cBuLMqBRrHaauzw@mail.gmail.com>

On Mon, Jul 25, 2011 at 6:01 AM, Jari Bakken <jari.bakken at gmail.com> wrote:

> On Fri, Jul 15, 2011 at 11:11 PM, Bret Pettichord <bret at pettichord.com>
> wrote:
> >
> > The big issue the remains open is the ownership and interface for
> > Watir::Browser. Watir and Watir-Webdriver have conflicting versions of
> this
> > module/class. Watir's version (actually in common-watir) is pluggable to
> use
> > different implementations of watir-compatable drivers. Watir-WebDriver's
> > assumes you are using webdriver for all browsers. What I would like to
> see
> > would be for Watir-Webdriver to rename its class and then update
> > Watir::Browser to user Watir-Webdriver as the default implementation for
> > Firefox and perhaps others.
> >
>
> So would renaming Watir::Browser to Watir::WebDriver in
> watir-webdriver solve this?
>
>
Yes it would.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/wtr-development/attachments/20110725/c403dd70/attachment.html>

From colinsdaddy at gmail.com  Mon Jul 25 14:06:45 2011
From: colinsdaddy at gmail.com (Hugh McGowan)
Date: Mon, 25 Jul 2011 13:06:45 -0500
Subject: [Wtr-development] Including Watir-WebDriver into Watir?
In-Reply-To: <CAPjkWY3mLCMweUJc9q7KAN2yfStuofgmUq5cBuLMqBRrHaauzw@mail.gmail.com>
References: <CAC1iRBzUi42rEv2YXPaPKgxju78an3sb4bfMpwHBomPCGAsrhg@mail.gmail.com>
	<CAPjkWY1gKsVPP0Sz9RtKE2JV=Ey9yq==hNW-JU8iDuNRdn-cUA@mail.gmail.com>
	<CAEMjNnLoCchvYp+MjyBpfYbks+BkA=Q3PLjEmpCkWviN=Ab_Sg@mail.gmail.com>
	<CAPjkWY3mLCMweUJc9q7KAN2yfStuofgmUq5cBuLMqBRrHaauzw@mail.gmail.com>
Message-ID: <CAH59Z1xzqRmpCxoUPFeTb5NQcoeXPX4gkVGmp0_wZtYadRy0PQ@mail.gmail.com>

Is there any problem we'd have with classes colliding in the Watir
namespace? My concern is that we define a Watir::TextField class in both the
webdriver and watir gems, which may lead to potential collisions. Would that
cause any issues or am I missing something?

Hugh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/wtr-development/attachments/20110725/51b62a02/attachment-0001.html>

From jarmo.p at gmail.com  Mon Jul 25 14:34:05 2011
From: jarmo.p at gmail.com (Jarmo)
Date: Mon, 25 Jul 2011 21:34:05 +0300
Subject: [Wtr-development] Including Watir-WebDriver into Watir?
In-Reply-To: <CAH59Z1xzqRmpCxoUPFeTb5NQcoeXPX4gkVGmp0_wZtYadRy0PQ@mail.gmail.com>
References: <CAC1iRBzUi42rEv2YXPaPKgxju78an3sb4bfMpwHBomPCGAsrhg@mail.gmail.com>
	<CAPjkWY1gKsVPP0Sz9RtKE2JV=Ey9yq==hNW-JU8iDuNRdn-cUA@mail.gmail.com>
	<CAEMjNnLoCchvYp+MjyBpfYbks+BkA=Q3PLjEmpCkWviN=Ab_Sg@mail.gmail.com>
	<CAPjkWY3mLCMweUJc9q7KAN2yfStuofgmUq5cBuLMqBRrHaauzw@mail.gmail.com>
	<CAH59Z1xzqRmpCxoUPFeTb5NQcoeXPX4gkVGmp0_wZtYadRy0PQ@mail.gmail.com>
Message-ID: <CAHZHd6Ug5RAA8G9b8vq6mPtgBxDOsON4FCk+-O+DCqdtd742BQ@mail.gmail.com>

If i understand the problem problem correctly then in Watir the
Watir::Browser is an "abstract browser class" to hide the implementation
classes behind it like Watir::IE and Watir::Firefox, but in Watir-WebDriver
the Watir::Browser is the implementation class itself. There's no problem
with having Watir::TextField in both places though.

Jarmo

On Mon, Jul 25, 2011 at 9:06 PM, Hugh McGowan <colinsdaddy at gmail.com> wrote:

> Is there any problem we'd have with classes colliding in the Watir
> namespace? My concern is that we define a Watir::TextField class in both the
> webdriver and watir gems, which may lead to potential collisions. Would that
> cause any issues or am I missing something?
>
> Hugh
>
> _______________________________________________
> Wtr-development mailing list
> Wtr-development at rubyforge.org
> http://rubyforge.org/mailman/listinfo/wtr-development
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/wtr-development/attachments/20110725/f1754308/attachment.html>

From jari.bakken at gmail.com  Mon Jul 25 15:02:11 2011
From: jari.bakken at gmail.com (Jari Bakken)
Date: Mon, 25 Jul 2011 21:02:11 +0200
Subject: [Wtr-development] Including Watir-WebDriver into Watir?
In-Reply-To: <CAH59Z1xzqRmpCxoUPFeTb5NQcoeXPX4gkVGmp0_wZtYadRy0PQ@mail.gmail.com>
References: <CAC1iRBzUi42rEv2YXPaPKgxju78an3sb4bfMpwHBomPCGAsrhg@mail.gmail.com>
	<CAPjkWY1gKsVPP0Sz9RtKE2JV=Ey9yq==hNW-JU8iDuNRdn-cUA@mail.gmail.com>
	<CAEMjNnLoCchvYp+MjyBpfYbks+BkA=Q3PLjEmpCkWviN=Ab_Sg@mail.gmail.com>
	<CAPjkWY3mLCMweUJc9q7KAN2yfStuofgmUq5cBuLMqBRrHaauzw@mail.gmail.com>
	<CAH59Z1xzqRmpCxoUPFeTb5NQcoeXPX4gkVGmp0_wZtYadRy0PQ@mail.gmail.com>
Message-ID: <AD79E4A2-74B0-4472-8ADA-C821C26BF739@gmail.com>



Den 25. juli 2011 kl. 20:06 skrev Hugh McGowan <colinsdaddy at gmail.com>:

> Is there any problem we'd have with classes colliding in the Watir namespace? My concern is that we define a Watir::TextField class in both the webdriver and watir gems, which may lead to potential collisions. Would that cause any issues or am I missing something?
> 

This would be an issue if there was a good reason to require both implementations in the same Ruby process. Is there? AFAICT one wouldn't gain anything from doing that. 

> Hugh
> _______________________________________________
> Wtr-development mailing list
> Wtr-development at rubyforge.org
> http://rubyforge.org/mailman/listinfo/wtr-development

From colinsdaddy at gmail.com  Mon Jul 25 15:23:04 2011
From: colinsdaddy at gmail.com (Hugh McGowan)
Date: Mon, 25 Jul 2011 14:23:04 -0500
Subject: [Wtr-development] Watir 2.0.0.rc2 released
In-Reply-To: <CAPjkWY3N-VzPnEc0gTycPz_6LSidLrqj_Jash75_-JPoG9uo2Q@mail.gmail.com>
References: <CAHZHd6XmJgCBPJob6YkVPcemcphEgTxDTAdZMmc_AZaqu+u4Sg@mail.gmail.com>
	<CAPjkWY3N-VzPnEc0gTycPz_6LSidLrqj_Jash75_-JPoG9uo2Q@mail.gmail.com>
Message-ID: <CAH59Z1x3rg0gVga5xfbsqdBTcvwLodDZxsw5wqZ=cQk=6tZsvw@mail.gmail.com>

Hi all,

I ran the unit tests for IE9/Win7/Ruby1.8.7 and made a few changes to fix
failing xpath tests (updated for zero-based indexing). Otherwise the release
looks great.

Thanks!
Hugh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/wtr-development/attachments/20110725/0e965bc7/attachment.html>

From colinsdaddy at gmail.com  Mon Jul 25 15:27:30 2011
From: colinsdaddy at gmail.com (Hugh McGowan)
Date: Mon, 25 Jul 2011 14:27:30 -0500
Subject: [Wtr-development] Including Watir-WebDriver into Watir?
In-Reply-To: <CAHZHd6Ug5RAA8G9b8vq6mPtgBxDOsON4FCk+-O+DCqdtd742BQ@mail.gmail.com>
References: <CAC1iRBzUi42rEv2YXPaPKgxju78an3sb4bfMpwHBomPCGAsrhg@mail.gmail.com>
	<CAPjkWY1gKsVPP0Sz9RtKE2JV=Ey9yq==hNW-JU8iDuNRdn-cUA@mail.gmail.com>
	<CAEMjNnLoCchvYp+MjyBpfYbks+BkA=Q3PLjEmpCkWviN=Ab_Sg@mail.gmail.com>
	<CAPjkWY3mLCMweUJc9q7KAN2yfStuofgmUq5cBuLMqBRrHaauzw@mail.gmail.com>
	<CAH59Z1xzqRmpCxoUPFeTb5NQcoeXPX4gkVGmp0_wZtYadRy0PQ@mail.gmail.com>
	<CAHZHd6Ug5RAA8G9b8vq6mPtgBxDOsON4FCk+-O+DCqdtd742BQ@mail.gmail.com>
Message-ID: <CAH59Z1y=GG6q6_i+18zc8em51U9CiojAWtz=H=yRj3mcF8eoCg@mail.gmail.com>

Awesome. Just wanted to make sure we didn't miss anything :)

Hugh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/wtr-development/attachments/20110725/f268764c/attachment.html>

From jarmo.p at gmail.com  Mon Jul 25 16:15:42 2011
From: jarmo.p at gmail.com (Jarmo)
Date: Mon, 25 Jul 2011 23:15:42 +0300
Subject: [Wtr-development] Watir 2.0.0.rc2 released
In-Reply-To: <CAH59Z1x3rg0gVga5xfbsqdBTcvwLodDZxsw5wqZ=cQk=6tZsvw@mail.gmail.com>
References: <CAHZHd6XmJgCBPJob6YkVPcemcphEgTxDTAdZMmc_AZaqu+u4Sg@mail.gmail.com>
	<CAPjkWY3N-VzPnEc0gTycPz_6LSidLrqj_Jash75_-JPoG9uo2Q@mail.gmail.com>
	<CAH59Z1x3rg0gVga5xfbsqdBTcvwLodDZxsw5wqZ=cQk=6tZsvw@mail.gmail.com>
Message-ID: <CAHZHd6VMP03-025Xazb3qKtJGT98kkA7Z0iuJKDpuQnhVRuz-w@mail.gmail.com>

Hmm, how come these tests failed for you on IE9 and not for me on IE8? Any
IE9 specific things?

I forgot to mention that for me the tests are passing against IE8/Win7/Ruby
1.8.7

Jarmo

On Mon, Jul 25, 2011 at 10:23 PM, Hugh McGowan <colinsdaddy at gmail.com>wrote:

> Hi all,
>
> I ran the unit tests for IE9/Win7/Ruby1.8.7 and made a few changes to fix
> failing xpath tests (updated for zero-based indexing). Otherwise the release
> looks great.
>
> Thanks!
> Hugh
>
> _______________________________________________
> Wtr-development mailing list
> Wtr-development at rubyforge.org
> http://rubyforge.org/mailman/listinfo/wtr-development
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/wtr-development/attachments/20110725/6193ad12/attachment.html>

From colinsdaddy at gmail.com  Mon Jul 25 16:45:51 2011
From: colinsdaddy at gmail.com (Hugh McGowan)
Date: Mon, 25 Jul 2011 15:45:51 -0500
Subject: [Wtr-development] Watir 2.0.0.rc2 released
In-Reply-To: <CAHZHd6VMP03-025Xazb3qKtJGT98kkA7Z0iuJKDpuQnhVRuz-w@mail.gmail.com>
References: <CAHZHd6XmJgCBPJob6YkVPcemcphEgTxDTAdZMmc_AZaqu+u4Sg@mail.gmail.com>
	<CAPjkWY3N-VzPnEc0gTycPz_6LSidLrqj_Jash75_-JPoG9uo2Q@mail.gmail.com>
	<CAH59Z1x3rg0gVga5xfbsqdBTcvwLodDZxsw5wqZ=cQk=6tZsvw@mail.gmail.com>
	<CAHZHd6VMP03-025Xazb3qKtJGT98kkA7Z0iuJKDpuQnhVRuz-w@mail.gmail.com>
Message-ID: <CAH59Z1yP74vahWV1-Y3dhrMOiEWp-f3p0GEY4W6x_GTb3cMe9Q@mail.gmail.com>

Did you run all_tests.rb or just the rake task? I don't think the xpath
tests get run in the latter.

Hugh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/wtr-development/attachments/20110725/c49899a0/attachment.html>

From bret at pettichord.com  Mon Jul 25 16:51:07 2011
From: bret at pettichord.com (Bret Pettichord)
Date: Mon, 25 Jul 2011 15:51:07 -0500
Subject: [Wtr-development] Watir 2.0.0.rc2 released
In-Reply-To: <CAHZHd6VMP03-025Xazb3qKtJGT98kkA7Z0iuJKDpuQnhVRuz-w@mail.gmail.com>
References: <CAHZHd6XmJgCBPJob6YkVPcemcphEgTxDTAdZMmc_AZaqu+u4Sg@mail.gmail.com>
	<CAPjkWY3N-VzPnEc0gTycPz_6LSidLrqj_Jash75_-JPoG9uo2Q@mail.gmail.com>
	<CAH59Z1x3rg0gVga5xfbsqdBTcvwLodDZxsw5wqZ=cQk=6tZsvw@mail.gmail.com>
	<CAHZHd6VMP03-025Xazb3qKtJGT98kkA7Z0iuJKDpuQnhVRuz-w@mail.gmail.com>
Message-ID: <CAPjkWY0kUmuZre98E8t0On8wkTwQ1OTExgw5hHZKe5RFS78pYA@mail.gmail.com>

We have seen more issues migrating to IE9 than with any previous IE upgrade.

Bret

On Mon, Jul 25, 2011 at 3:15 PM, Jarmo <jarmo.p at gmail.com> wrote:

> Hmm, how come these tests failed for you on IE9 and not for me on IE8? Any
> IE9 specific things?
>
> I forgot to mention that for me the tests are passing against IE8/Win7/Ruby
> 1.8.7
>
> Jarmo
>
> On Mon, Jul 25, 2011 at 10:23 PM, Hugh McGowan <colinsdaddy at gmail.com>wrote:
>
>> Hi all,
>>
>> I ran the unit tests for IE9/Win7/Ruby1.8.7 and made a few changes to fix
>> failing xpath tests (updated for zero-based indexing). Otherwise the release
>> looks great.
>>
>> Thanks!
>> Hugh
>>
>> _______________________________________________
>> 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
>



-- 
Bret Pettichord
Director, Watir Project, www.watir.com

Blog, www.testingwithvision.com
Twitter, www.twitter.com/bpettichord
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/wtr-development/attachments/20110725/ce4de4ae/attachment.html>

From jarmo.p at gmail.com  Mon Jul 25 16:58:40 2011
From: jarmo.p at gmail.com (Jarmo)
Date: Mon, 25 Jul 2011 23:58:40 +0300
Subject: [Wtr-development] Watir 2.0.0.rc2 released
In-Reply-To: <CAH59Z1yP74vahWV1-Y3dhrMOiEWp-f3p0GEY4W6x_GTb3cMe9Q@mail.gmail.com>
References: <CAHZHd6XmJgCBPJob6YkVPcemcphEgTxDTAdZMmc_AZaqu+u4Sg@mail.gmail.com>
	<CAPjkWY3N-VzPnEc0gTycPz_6LSidLrqj_Jash75_-JPoG9uo2Q@mail.gmail.com>
	<CAH59Z1x3rg0gVga5xfbsqdBTcvwLodDZxsw5wqZ=cQk=6tZsvw@mail.gmail.com>
	<CAHZHd6VMP03-025Xazb3qKtJGT98kkA7Z0iuJKDpuQnhVRuz-w@mail.gmail.com>
	<CAH59Z1yP74vahWV1-Y3dhrMOiEWp-f3p0GEY4W6x_GTb3cMe9Q@mail.gmail.com>
Message-ID: <CAHZHd6XhpvaCQ4s9akyny8NioDX_Q6V+1hhakabzeJuvK-0ntw@mail.gmail.com>

You're correct, i didn't run all_tests. Nice that there weren't many hidden
failures then :)

J.

On Mon, Jul 25, 2011 at 11:45 PM, Hugh McGowan <colinsdaddy at gmail.com>wrote:

> Did you run all_tests.rb or just the rake task? I don't think the xpath
> tests get run in the latter.
>
> Hugh
>
> _______________________________________________
> Wtr-development mailing list
> Wtr-development at rubyforge.org
> http://rubyforge.org/mailman/listinfo/wtr-development
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/wtr-development/attachments/20110725/36e049d4/attachment-0001.html>

From colinsdaddy at gmail.com  Mon Jul 25 17:23:14 2011
From: colinsdaddy at gmail.com (Hugh McGowan)
Date: Mon, 25 Jul 2011 16:23:14 -0500
Subject: [Wtr-development] Watir 2.0.0.rc2 released
In-Reply-To: <CAHZHd6XhpvaCQ4s9akyny8NioDX_Q6V+1hhakabzeJuvK-0ntw@mail.gmail.com>
References: <CAHZHd6XmJgCBPJob6YkVPcemcphEgTxDTAdZMmc_AZaqu+u4Sg@mail.gmail.com>
	<CAPjkWY3N-VzPnEc0gTycPz_6LSidLrqj_Jash75_-JPoG9uo2Q@mail.gmail.com>
	<CAH59Z1x3rg0gVga5xfbsqdBTcvwLodDZxsw5wqZ=cQk=6tZsvw@mail.gmail.com>
	<CAHZHd6VMP03-025Xazb3qKtJGT98kkA7Z0iuJKDpuQnhVRuz-w@mail.gmail.com>
	<CAH59Z1yP74vahWV1-Y3dhrMOiEWp-f3p0GEY4W6x_GTb3cMe9Q@mail.gmail.com>
	<CAHZHd6XhpvaCQ4s9akyny8NioDX_Q6V+1hhakabzeJuvK-0ntw@mail.gmail.com>
Message-ID: <CAH59Z1z+t-fH2VJ8hoLm4CF=NurRHqx-PSieDz6S6Gay3yhJ9Q@mail.gmail.com>

Yeah, we may just want to change that and have the rake task always run all
the tests. I can't think of a good reason to run a subset when it takes a
minute or two to run.

Hugh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/wtr-development/attachments/20110725/76eacce6/attachment.html>

From jarmo.p at gmail.com  Fri Jul 29 15:11:50 2011
From: jarmo.p at gmail.com (Jarmo)
Date: Fri, 29 Jul 2011 22:11:50 +0300
Subject: [Wtr-development] Watir 2.0.0.rc2 released
In-Reply-To: <CAH59Z1z+t-fH2VJ8hoLm4CF=NurRHqx-PSieDz6S6Gay3yhJ9Q@mail.gmail.com>
References: <CAHZHd6XmJgCBPJob6YkVPcemcphEgTxDTAdZMmc_AZaqu+u4Sg@mail.gmail.com>
	<CAPjkWY3N-VzPnEc0gTycPz_6LSidLrqj_Jash75_-JPoG9uo2Q@mail.gmail.com>
	<CAH59Z1x3rg0gVga5xfbsqdBTcvwLodDZxsw5wqZ=cQk=6tZsvw@mail.gmail.com>
	<CAHZHd6VMP03-025Xazb3qKtJGT98kkA7Z0iuJKDpuQnhVRuz-w@mail.gmail.com>
	<CAH59Z1yP74vahWV1-Y3dhrMOiEWp-f3p0GEY4W6x_GTb3cMe9Q@mail.gmail.com>
	<CAHZHd6XhpvaCQ4s9akyny8NioDX_Q6V+1hhakabzeJuvK-0ntw@mail.gmail.com>
	<CAH59Z1z+t-fH2VJ8hoLm4CF=NurRHqx-PSieDz6S6Gay3yhJ9Q@mail.gmail.com>
Message-ID: <CAHZHd6UZb-8iLX5KBd_+Nf4f0YXDTTuxwi3OyM3TN3W4Qp72KA@mail.gmail.com>

It's been some time now since rc has been out. Haven't seen much of a
feedback from someone actually trying this version with their current tests.
Having that in mind i'd like to try it myself against our tests in my
workplace. I'd like to do that in the beginning of next week.

I'm encouraging you to try it out as well.

Jarmo

On Tue, Jul 26, 2011 at 12:23 AM, Hugh McGowan <colinsdaddy at gmail.com>wrote:

> Yeah, we may just want to change that and have the rake task always run all
> the tests. I can't think of a good reason to run a subset when it takes a
> minute or two to run.
>
> Hugh
>
> _______________________________________________
> Wtr-development mailing list
> Wtr-development at rubyforge.org
> http://rubyforge.org/mailman/listinfo/wtr-development
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/wtr-development/attachments/20110729/7f6e5d60/attachment.html>

From colinsdaddy at gmail.com  Fri Jul 29 16:31:56 2011
From: colinsdaddy at gmail.com (Hugh McGowan)
Date: Fri, 29 Jul 2011 15:31:56 -0500
Subject: [Wtr-development] Watir 2.0.0.rc2 released
In-Reply-To: <CAHZHd6UZb-8iLX5KBd_+Nf4f0YXDTTuxwi3OyM3TN3W4Qp72KA@mail.gmail.com>
References: <CAHZHd6XmJgCBPJob6YkVPcemcphEgTxDTAdZMmc_AZaqu+u4Sg@mail.gmail.com>
	<CAPjkWY3N-VzPnEc0gTycPz_6LSidLrqj_Jash75_-JPoG9uo2Q@mail.gmail.com>
	<CAH59Z1x3rg0gVga5xfbsqdBTcvwLodDZxsw5wqZ=cQk=6tZsvw@mail.gmail.com>
	<CAHZHd6VMP03-025Xazb3qKtJGT98kkA7Z0iuJKDpuQnhVRuz-w@mail.gmail.com>
	<CAH59Z1yP74vahWV1-Y3dhrMOiEWp-f3p0GEY4W6x_GTb3cMe9Q@mail.gmail.com>
	<CAHZHd6XhpvaCQ4s9akyny8NioDX_Q6V+1hhakabzeJuvK-0ntw@mail.gmail.com>
	<CAH59Z1z+t-fH2VJ8hoLm4CF=NurRHqx-PSieDz6S6Gay3yhJ9Q@mail.gmail.com>
	<CAHZHd6UZb-8iLX5KBd_+Nf4f0YXDTTuxwi3OyM3TN3W4Qp72KA@mail.gmail.com>
Message-ID: <CAH59Z1y2ze5x9-VQkonu1-tzvcHRFdeZp9Dhevy5M3gNPpZXng@mail.gmail.com>

I'll try it out next week too - this week we've been rolling out a release
so it's been crazy.

Hugh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/wtr-development/attachments/20110729/c3ec32b3/attachment.html>