Watir 1.6.5.rc1 - release candidate available for testing

[Charley Baker]

Hi all,

 There have been a lot of changes since the last release of Watir - 1.6.2, many of these being contributions we've received from various community members, core committers and others. In the effort to include Firewatir as a 1st class citizen, there are a lot compatibility changes and refactorings in this release, many platform issues have been taken care of, as well as api differences. The list of changes is included below.

 This is being released as a true release candidate for the first time (given rubygems support in 1.3.2+ for this type of release) which among other reasons is why we're requesting you update rubygems . Please report any issues with detailed information - platform, ruby version, error trace, test run and html from the SUT, if this is a new failure with the current version of watir. The more platforms we can run this on the better to detect any issues. Success for running your current tests based on platform is also good to hear.
 
 Installation instructions are here. The final build will be posted on rubyforge and tagged in github, with news to update to the final version.
http://wiki.openqa.org/display/WTR/Development+Builds


Thanks for your help,

Charley

== Version 1.6.5.rc1
 
This is a release candidate.
 
=== New Features (Both IE and Firefox)
 
* Browser.attach is now available.
* Browser.options and Browser.set_options are now available.
* Add support for definition lists, this adds these methods:
  dd, dt, dl, dds, dts, dls. (Jarib)
* Hidden#visible? should always return false. (Jarib)
* New method execute_script.
* Add ElementCollections#size as alias of length. (Jarib)
* Some camelCase => snake_case renames (with aliasing). (Jarib)
    Image#fileCreatedDate       => file_created_date
    Image#fileSize              => file_size
    Image#hasLoaded?            => loaded?
    SelectList#getAllContents   => options
    SelectList#getSelectedItems => selected_options
    SelectList#clearSelection   => clear
    SelectList#includes?        => include?
    TextField#dragContentsTo    => drag_contents_to
    Radio/Checkbox#isSet?       => set?
* Patch for winclicker fix. http://jira.openqa.org/browse/WTR-279 (Derek Berner)
* Add support for using a Regexp as the third argument (value) when locating
  checkboxes/radio buttons. (Jarib)
* Add support for <strong> element. (Jarib)
* Add support and tests for <em> element. (Jarib)
* SelectList#select now supports Numeric arguments. (Jarib)
* Additional inspect implementations for both IE and FF. (Jarib)
* Added ElementCollections#{first,last}. (Jarib)
* Fixes for running on Ruby 1.9. (Jarib)
 
=== Firefox Improvements
 
* SelectList#set is now defined for Firefox. Like with IE, it is an alias for
  SelectList#select. [271]
* Element collections are now enumerable. This allows methods such as @select@
  and @map@ to be used with methods such as @divs@ and @links@.
* FireWatir.attach is now available, analogous to IE.attach.
* Some Javascript errors that were being ignored, now raise Ruby exceptions.
* Added event handler which resets the context of document
* Fix bug that occurred when new page was automatically loaded. (Angrez, 3ef8b6)
  when page gets loaded automatically (Angrez)
* Changed code to use document_var, body_var, window_var, browser_var instead of
  "document", "body", "window", "browser" variables. (Angrez)
* Changed code to replace every quote (") in xpath query with (\") so that it
  doesn't give error while executing the xpath query (Angrez)
* Fire onchange event for FireWatir file fields. Closes WTR-286. (Jarib)
* Fixes for running and closing Firefox on Mac OS X
* added functionality to allow Watir::Browser.attach with no arguments to open
 a new firefox window rather than taking over the existing focused window (Rob Aldred)
* also modified some setup functions to correctly handle closed browsers,
 browserless windows and others (Rob Aldred)
* Add test and implementation for Firefox#status http://jira.openqa.org/browse/WTR-250 (Jarib)
 
=== IE Improvements
 
* Allow attach timeout to be accessed as an option. Thus:
    IE.set_options :attach_timeout => 5.0
  This was previously available as class method.
* Fix for Autoit auto-registration. (Bret)
* Fix for IE6, 7 and 8 file downloads. (Željko Filipin & Jarmo Pertman)
* Replaced REXML with Nokogiri for xml parsing. (Aidy Lewis)
* Option now supports :label attribute http://jira.openqa.org/browse/WTR-297
* Patch for IE.close causing WIN32OLE errors http://jira.openqa.org/browse/WTR-304 (Tony)
* Watir::IE.inspect issue fixed: http://jira.openqa.org/browse/WTR-180 (Jarib)
* Fix for Browser#execute_script on IE7. (Jarib)
* Removed ActiveSupport dependency. (Jarib)
 
=== Structure Improvements
 
* Lots of rework of the FireWatir code, including removing duplication and
  dead code, renaming variables, and simplifying code. Also a few performance
  improvements.
* Rename source file names for consistency.
 
=== Unit Tests
 
* Add tests demonstrating known bugs.
* Make the "window" tests run more reliably.
* Relocate unreliable tests.
* Tag tests that are known to fail on IE or Firefox.
* Fixed one test that was failing on non-English platforms. (Jarib)
* New Rake task (:test) runs all tests.
* Use ci_reporter to provide more detailed test results for watirbuild.com.
  Use xls transform to format results.
 

Charley Baker
blog: http://blog.charleybaker.org/
Lead Developer, Watir, http://wtr.rubyforge.org
QA Architect, Gap Inc Direct

[Željko Filipin]

`gem update --system` took something like an hour after a clean Ruby 1.8.6-26 install. I know we can not do anything about it, but I was _really_ surprised.

Željko
--
http://watirpodcast.com/

[aidy lewis]

Hi Charley

2009/10/5 Charley Baker <charle...@gmail.com>: wrote:

> http://wiki.openqa.org/display/WTR/Development+Builds

Would it not be an idea to install the gem(s) directly from github?

Aidy

[Charley Baker]

I'd thought about doing something like that. Unfortunately it's somewhat of a moot point right now since github's gem creation isn't working since the switch to rackspace. :) That's probably the way to go next time though.

Charley Baker
blog: http://blog.charleybaker.org/
Lead Developer, Watir, http://wtr.rubyforge.org
QA Architect, Gap Inc Direct

[Bret Pettichord]

Another problem is that github only allowed one gem per project. We
currently have three.

On Oct 9, 10:33 am, Charley Baker <charley.ba...@gmail.com> wrote:
> I'd thought about doing something like that. Unfortunately it's somewhat of
> a moot point right now since github's gem creation isn't working since the
> switch to rackspace. :) That's probably the way to go next time though.
>
> Charley Baker
> blog:http://blog.charleybaker.org/

> Lead Developer, Watir,http://wtr.rubyforge.org

> QA Architect, Gap Inc Direct
>

> On Fri, Oct 9, 2009 at 8:18 AM, aidy lewis <aidy.le...@googlemail.com>wrote:
>
>
>
> > Hi Charley
>

[Charley Baker]

Good point. Also I spoke too soon. Github is no longer going to support gem building - blog from yesterday: http://github.com/blog/515-gem-building-is-defunct
The new solution is to use gemcutter and jeweler - gemcutter.org, http://github.com/technicalpickles/jeweler

Interesting new development. Watir gems are currently up on gemcutter, pulled from Rubyforge from 1.6.2. We'll have to take a look at setting this up.

-Charley

[Željko Filipin]

On Fri, Oct 9, 2009 at 4:04 PM, Željko Filipin <zeljko....@wa-research.ch> wrote:
> `gem update --system` took something like an hour after a clean Ruby 1.8.6-26 install

"gem update --system --no-rdoc --no-ri" took a long time too, but probably only 1/3 or 1/2 of full install, I did not measure. Should we recommend that? I never use rdoc or ri, but I do not know if other people use it.

Željko

[Charley Baker]

Wow, it didn't take very long for me, 5mins tops. Not sure why it took so long. I generally go no ri, no rdoc as well, nice tip if you're not using it, some people do.

-c

[Željko Filipin]

On Sat, Oct 10, 2009 at 12:07 AM, Charley Baker <charle...@gmail.com> wrote:
> Wow, it didn't take very long for me, 5mins tops.

My example was after a clean Ruby install. I guess it does not take so long if you have never version of rubygems.

Željko

[Bret Pettichord]

I wonder if this is because the gem server is in the united states.

bret

On Oct 9, 5:10 pm, Željko Filipin <zeljko.fili...@wa-research.ch>
wrote:
> On Sat, Oct 10, 2009 at 12:07 AM, Charley Baker <charley.ba...@gmail.com>

[Bret Pettichord]

Interesting.

Charley Baker wrote:
> Good point. Also I spoke too soon. Github is no longer going to
> support gem building - blog from yesterday:
> http://github.com/blog/515-gem-building-is-defunct
> The new solution is to use gemcutter and jeweler - gemcutter.org

> <http://gemcutter.org>, http://github.com/technicalpickles/jeweler

>
> Interesting new development. Watir gems are currently up on gemcutter,
> pulled from Rubyforge from 1.6.2. We'll have to take a look at setting
> this up.
>
> -Charley
>
>
> On Fri, Oct 9, 2009 at 10:14 AM, Bret Pettichord
> <bpett...@gmail.com <mailto:bpett...@gmail.com>> wrote:
>
>
> Another problem is that github only allowed one gem per project. We
> currently have three.
>
> On Oct 9, 10:33 am, Charley Baker <charley.ba...@gmail.com

> <mailto:charley.ba...@gmail.com>> wrote:
> > I'd thought about doing something like that. Unfortunately it's
> somewhat of
> > a moot point right now since github's gem creation isn't working
> since the
> > switch to rackspace. :) That's probably the way to go next time
> though.
> >
> > Charley Baker
> > blog:http://blog.charleybaker.org/
> > Lead Developer, Watir,http://wtr.rubyforge.org
> > QA Architect, Gap Inc Direct
> >
> > On Fri, Oct 9, 2009 at 8:18 AM, aidy lewis

> <aidy.le...@googlemail.com <mailto:aidy.le...@googlemail.com>>wrote:

> >
> >
> >
> > > Hi Charley
> >
> > > 2009/10/5 Charley Baker <charley.ba...@gmail.com

> <mailto:charley.ba...@gmail.com>>: wrote:
> >
> > > >http://wiki.openqa.org/display/WTR/Development+Builds
> >
> > > Would it not be an idea to install the gem(s) directly from
> github?
> >
> > > Aidy
>
>
>
> >

--
Bret Pettichord
Lead Developer, Watir, www.watir.com
Blog, www.io.com/~wazmo/blog
Twitter, www.twitter.com/bpettichord

[Željko Filipin]

- all examples at Windows 2003 Server machine

1) clean Watir 1.6.5
- uninstall Ruby
- install ruby186-26.exe
- update rubygems
- install watir-1.6.5.rc1.gem
- everything is fine

2) clean Watir 1.6.2
- uninstall Ruby
- install ruby186-26.exe
- update rubygems
- install Watir 1.6.2
- everything is fine

3) upgrade Watir from 1.6.2 to 1.6.5.
- machine with Watir 1.6.2 (from the second example)
- install watir-1.6.5.rc1.gem

>gem install watir --no-rdoc --no-ri
Successfully installed commonwatir-1.6.5.rc1
Successfully installed nokogiri-1.3.3-x86-mswin32
Successfully installed watir-1.6.5.rc1
3 gems installed

- firewatir 1.6.5. was not installed
- sample IRB session

irb(main):001:0> require "watir"
=> true
irb(main):002:0> puts Watir::IE::VERSION
LoadError: no such file to load -- watir/ie
        from (irb):2
irb(main):003:0> b = Watir::IE.new
NameError: uninitialized constant Watir::IE
        from (irb):3
irb(main):004:0> b = Watir::Browser.new
LoadError: (eval):1:in `klass': no such file to load -- firewatir
        from c:/ruby/lib/ruby/gems/1.8/gems/commonwatir-1.6.5.rc1/lib/watir/browser.rb:89:in `klass'
        from c:/ruby/lib/ruby/gems/1.8/gems/commonwatir-1.6.5.rc1/lib/watir/browser.rb:65:in `eval'
        from c:/ruby/lib/ruby/gems/1.8/gems/commonwatir-1.6.5.rc1/lib/watir/browser.rb:89:in `klass'
        from c:/ruby/lib/ruby/gems/1.8/gems/commonwatir-1.6.5.rc1/lib/watir/browser.rb:65:in `new'
        from (irb):4

[Željko Filipin]

The upgrade works fine if I first uninstall 1.6.2 versions of watir, firewatir and commonwatir, and then install 1.6.5.

Željko

[Željko Filipin]

If you get this:

>gem update --system
Updating RubyGems
Nothing to update

>gem -v
1.2.0

you should read this:

http://stackoverflow.com/questions/566614/how-can-i-force-gem-to-upgrade-to-gem-1-3-1
http://soft-dev-pro.blogspot.com/2009/07/update-rubygems.html

Probably the easiest way to update rubygems 1.2.0 is to reinstall ruby and then update rubygems.

Željko

[Željko Filipin]

Executed all my tests with Watir 1.6.5. Just one failure, Watir now sees Spanish characters differently. Fixed that and everything works just fine.

[Bret Pettichord]

We have a fix for this and it will be included in RC2.

[Željko Filipin]

On Fri, Oct 9, 2009 at 10:21 PM, Željko Filipin <zeljko....@wa-research.ch> wrote:
> "gem update --system --no-rdoc --no-ri" took a long time too, but probably only 1/3 or 1/2 of full install, I did not measure.

I have added this text to http://watir.com/installation/:

Tip: While updating RubyGems, you can use gem update --system --no-rdoc --no-ri instead of gem update --system. It will be much faster, but you will not install RDoc and ri.

Please let me know if you think it should be changed or removed.

Željko