two links on this page  http://wiki.openqa.org/display/WTR/Example+Test+Case

right below the header "google test search"

They point at:
  http://svn.openqa.org/svn/watir/trunk/watir/examples/google_search.rb
  http://svn.openqa.org/svn/watir/trunk/watir/examples/


On Nov 10, 7:51 am, Bret Pettichord <[EMAIL PROTECTED]> wrote:
> It is unclear to me what examples you mean.
>
> Examples that had been included in the 1.5 source tree were moved to the
> wiki.http://wiki.openqa.org/display/WTR/Examples
>
> Bret
>
>
>
> Chuck vdL wrote:
> > I think I found them back on the 1.5 branch, but the trunk based links
> > to the Examples folder given in the tutorial are no longer working.
>
> > I installed watir just before you bumped to 1.6  but have been busy
> > with other things at work and was just now starting on the tutorial.
>
> > Is someone slated to go through the tutorial examples and make sure
> > they work correctly with 1.6?   If not I suppose I could try doing
> > this, since I'm a totally fresh set of eyes that might be good, but
> > since I'm new to watir and ruby it might be a wee bit difficult for me
> > to differentiate between my own mistakes and errors due to changes in
> > 1.6
>
> > I suppose I can set-up a different VM or snapshot tree and put 1.6 on
> > it, and then compare the results with the existing VM I've got 1.5
> > installed on..  (total Hyper-V addict here), which should allow me to
> > tell if the code works on one and not the other.- Hide quoted text -
>
> - Show quoted text -
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Watir General" group.
To post to this group, send email to watir-general@googlegroups.com
Before posting, please read the following guidelines: 
http://wiki.openqa.org/display/WTR/Support
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/watir-general
-~----------~----~----~----~------~----~------~--~---

Reply via email to