Thanks Chris,
FYI, I uninstalled Ruby 186-25 and Watir 1.5.1.1158 from this machine that
fails. The OLE version from this prior install was showing 0.7.1. I loaded
Ruby 185-21 and Watir 1.5.1.1136 on my failing machine and still see the
problem. I have this same version (Ruby 185-21 / Watir
Ruby 182-15, Watir 1.5.1.1136
works fine
___
Wtr-general mailing list
Wtr-general@rubyforge.org
http://rubyforge.org/mailman/listinfo/wtr-general
Hi Chris,
Sorry I haven't been back on this one: I only have access to the
machine on which I have the problem on Thursdays (long story), and I
missed last week's session altogether.
On 26/03/07, Chris McMahon <[EMAIL PROTECTED]> wrote:
> I run Brad's code with no problem (thanks for the example!)
Sorry I can't help more.
I'm using ruby 1.8.5 (2006-08-25) and Watir 1.5.1.1158, WinXP.
You might try playing with OLE directly. For instance, try to move
object from Paint to Word, or something. See if you can get the same
error from pure MS applications.
-C
On 3/26/07, Brad <[EMAIL PROTECTED
Thanks Chris,
I just did the following and see the same error:
* uninstalled Ruby 186-25
* reboot PC
* installed Ruby 186-25 using Windows installer
* run latest Watir gem 1.5.1.1158
This use to work on an earlier version Ruby (185-21) and Watir (1.5.1.1136) but
left this for a while (over a mo
I run Brad's code with no problem (thanks for the example!).
Googling, I find that "IEnum interface" is an error coming from Ruby's
WIN32OLE library. The root cause seems to be some kind of error in
the interface between Ruby and Windows on the particular machine.
One very suggestive issue is th
I'm seeing the same error on my environment. Here is the same code along with
the error.
Code:
require 'rubygems'
require 'watir'
include Watir
#require 'watir_ext' # extension to watir for 'visible?'
#include Watir
require 'test/unit'
require 'csv'
puts Watir::IE::VERSION # check for WAT
> Nop,e checked that. Besides, the irb session I pasted is verbatim.
Run the unit tests from the command line and check the output. At the
*very end* of the entire run (that is, don't kill the process in the
middle), you should have some "..." characters, some "F" characters,
followed by the pas
Hi Chris,
On 15/03/07, Chris McMahon <[EMAIL PROTECTED]> wrote:
> On 3/15/07, Kevin Rutherford <[EMAIL PROTECTED]> wrote:
> > Hi,
> > Does anyone have any idea what's broken in my environment please?
> > Many thanks,
> > Kevin
>
> Different versions of Ruby maybe?
Both machines running 1.8.5
On 3/15/07, Kevin Rutherford <[EMAIL PROTECTED]> wrote:
> Hi,
> Does anyone have any idea what's broken in my environment please?
> Many thanks,
> Kevin
Different versions of Ruby maybe?
BTW, there is detailed information about which tests didn't pass. I
think it goes to STDERR, though, not
Hi,
Does anyone have any idea what's broken in my environment please?
Many thanks,
Kevin
On 09/03/07, Kevin Rutherford <[EMAIL PROTECTED]> wrote:
> Hi,
> I know this question has been asked before, but I didn't see a
> resolution in the list archives...
>
> I have just installed Watir onto tw
Hi,
I know this question has been asked before, but I didn't see a
resolution in the list archives...
I have just installed Watir onto two different machines. On one,
everything works fine (and Watir's tests all pass). But on the other
I have a problem. Firstly, the Watir gem's tests don't pass
12 matches
Mail list logo
