Other than changing the logic of how you are locating frames, the only
thing I could find that dealt with suppression of warnings might be:
ie.logger.level = Logger::ERROR
As I don't have your code to test this solution, it's really a
glorified guess. I'd be more inclined to approach the frame
Is there a chance you're testing a great number of pages? My only
experience with this behavior was for testing around 20k pages in one
script -- Internet Explorer would always croak after 5-8k pages. I
switched to WWW::Mechanize for that script and it ran to completion.
My tests were also on
I reinstalled watir 1.6.5 and this appears to be working across the
board now. Not sure what was wrong with my installation. Thanks for
the replies in working this out!
On Feb 10, 10:27 pm, AR reed.a...@gmail.com wrote:
Error is either Nil, or an error saying element not found depending
on my
One of our developers has been trying to make clearer hooks for my
WATIR development efforts. We're testing a theory using custom tags
to see if I can access elements, and after following the advice here
and on Zeljko's blog, I'm running into an interesting issue.
These examples are not in an
(:index, 1).attribute_value(qa)
*
*
*I have the same Watir, ruby version, windows version as you.*
*I think you may try the code again.*
*
*
Wesley.
For life, the easier, the better.
On Thu, Feb 11, 2010 at 6:28 AM, AR reed.a...@gmail.com wrote:
@ie.text_field(:xpath, //inp...@qa
pm, Wesley Chen cjq@gmail.com wrote:
No, I use:
ruby 1.8.6 (2007-09-24 patchlevel 111) [i386-mswin32]
Watir 1.6.5
What's your error message?
I think your *text_field* part is not the same as mine.
Wesley.
For life, the easier, the better.
On Thu, Feb 11, 2010 at 9:23 AM, AR reed.a
It's not part of SafariWatir, but rather the fileutils library.
You're manually deleting the information in the directory where
cookies are stored. Safari may store them in another location, but
the principle is the same:
require 'fileutils'
$cookieDir = C:\\Documents and
Thanks for this! I've run into that same issue with irb from time to
time, but just chalked it up to dealing with it. I use irb a lot for
step by step development or concept testing before I invest in an
organized and commented script. I'm not sure how you're using the
#{libs} variable, so I
I'm able to use begin/rescue/end for 99% of cases. Normally I'll
collect the error into an array for logging or an email report
afterward. Using those conventions, the script never stops, and I
don't have to be glued to the console to find out when it breaks.
On Feb 4, 1:42 pm, tester86
You can also set visible:false in the the options.yml file if you
don't want to do it on a script by script basis.
More details here: http://wiki.openqa.org/display/WTR/Browser.new
On Feb 4, 11:37 am, orde ohil...@gmail.com wrote:
You can set the browser as invisible after launching the browser
Howdy. Can you please paste the relevant code and any errors/output
that you may be getting? What exactly happens instead of the expected
behavior? Also, if you're able to share the site that you're testing,
that might help.
Thanks,
Adam
On Jan 19, 4:07 am, xguarder shams...@gmail.com wrote:
, this might be a viable solution for you. The
WWW::Mech version of my script was just over 8 lines; pretty simple.
Adam
On Sep 8, 11:12 am, AR reed.a...@gmail.com wrote:
I've had the same issue while doing a little sanity checking on some
marketing websites that we control. Using IE.new_process
I've had the same issue while doing a little sanity checking on some
marketing websites that we control. Using IE.new_process helped a
little, but Ruby would always die before the script completed.
On Aug 30, 6:33 pm, Chris McMahon christopher.mcma...@gmail.com
wrote:
looks to me that
a) Yes, of course!
b) The error looks like it's being thrown from 'example_logger1' - can
you please post the source of that file? Keeping the line numbers in
errors helps, too -- it looks like you have removed them.
On May 11, 7:55 am, ash ashbr...@gmail.com wrote:
Having successfully
Nevermind, I'm blind. Line numbers still would have helped :D
On May 11, 11:03 am, AR reed.a...@gmail.com wrote:
a) Yes, of course!
b) The error looks like it's being thrown from 'example_logger1' - can
you please post the source of that file? Keeping the line numbers in
errors helps, too
://rubyonwindows.blogspot.com/search/label/excel
Hope this helps!
-Tiffany
On Apr 28, 12:43 pm, AR reed.a...@gmail.com wrote:
I've checked all the usual suspects (rubygarden article, searching
here, etc), but I haven't found the functionality for renaming an
Excel worksheet (NOT workbook
Just to make sure I understand, let's lay out a basic rescue.
-- code --
begin
assertion
actions if assertion passes
rescue
actions if assertion failed
end #rescue block
-- unrelated actions/functions here --
It sounds like you want the rescue to force the program to end safely
rather
I was getting the same error when I first set up my new environment.
I started Firefox manually via the command line once with the JSSH
option enabled, and have not seen the problem since that time. Not
sure exactly why this was necessary, but this was the only change I
made while testing the
I'm also a big fan of Marick's Everyday Scripting with Ruby:
http://www.pragprog.com/titles/bmsft/everyday-scripting-with-ruby
On Apr 3, 2:54 pm, Lisa Crispin lisa.cris...@gmail.com wrote:
I mentioned it!
On Fri, Apr 3, 2009 at 10:44 AM, Paul Rogers paul.rog...@shaw.ca wrote:
im
I'm getting this strange error after our Ops team built us some new
testing VMs. I installed Ruby and Watir, and am getting the same
error for anything that includes Watir. I can go into IRB and do Ruby
all day, but as soon as I enter ie = Watir::IE.new, I get the
following error. Has anyone
/
ri --title
Builder -- Easy XML Building --main README --line-numbers --quiet lib
CHANGES Ra
kefile README doc/releases/builder-1.2.4.rdoc doc/releases/
builder-2.0.0.rdoc do
c/releases/builder-2.1.1.rdoc
(continuing with the rest of the installation)
On Feb 24, 9:24 am, AR reed.a...@gmail.com wrote
time and only concerns the
documentation for builder. I has no effect on the way it runs.
Jim
On Feb 24, 10:20 am, AR reed.a...@gmail.com wrote:
While viewing the watir installation again, I do get one error, but it
seems to be fairly innocuous:
ERROR: While generating documentation
, Feb 24, 2009 at 9:42 AM, AR reed.a...@gmail.com wrote:
Thanks Jim - I guess that leaves me with no leads. I attempted the
install again on another VM with the same 14001 error. Google is
especially dry on this topic - has no one seen this before?
Adam
On Feb 24, 10:34 am, Jim Matthews
gem. Lots of others are having
problems with this as well, as you'll see if read some of the other
active threads. Right now, best solution is to uninstall ruby,
reinstall, and pray. We are working to better understand the details.
Bret
AR wrote:
Thanks Jim - I guess that leaves me
I've been having some issues with scripts that ask IE to visit a lot
of URLs eventually killing IE and failing. In these instances,
ruby.exe is sitting right around 30Mb of memory, Excel (used to import
data) is around 5Mb, and IE works itself up from 100Mb to 1.5Gb.
At it's most basic point, I
On Jan 7, 4:14 pm, Bret Pettichord b...@pettichord.com wrote:
Try Watir::IE.new_process instead. This will open (and then close) a
process each time, and therefore should avoid the memory leak.
The funny thing about this one is that I'm using $HIDE_IE=true, and
now each new browser window
26 matches
Mail list logo
