Hey gang,
I developed a very robust framework for a company in 2009-2011 using watir
and converted to watir-webdriver in late 2011- early 2012. During the
conversion I had to make many horrible compromises (inserting retry
statements, wait statements, etc.), and watir-webdriver still gave
Ah, I read it too fast. Thanks Zeljko.
On Jan 17, 3:54 am, Željko Filipin zeljko.fili...@gmail.com wrote:
On Mon, Jan 16, 2012 at 6:19 PM, jw joshuawal...@gmail.com wrote:
Zeljko, thanks for taking the time to organize the information around
Watir. I saw one bullet that I have a question
Thanks Chuck. What you said is not surprising after reading the
code. What is surprising is that WW implements the whole Watir API
(with some differences as we've all seen). I think WW gem requires
common-watir and I thought Watir, but if you say it does not then I'm
sure you're right. I
So to be clear, the change to (for example) Button#text would not
affect a script that uses watir-webdriver, correct? Is there any
noticeable change to watir-webdriver users?
Thanks for keeping people writing automation at their job instead of
testing manually!
On Jan 13, 1:32 am, Jarmo
This question was spawned when Jarmo recently announced watir 3.0. I
was trying to figure out if the changes he listed would affect my
watir-webdriver scripts, and after looking at some code I'm guessing
not.
When I've installed watir-webdriver it seems watir is a prereq. But I
noticed that
After searching for a long time, Alister Scott finally clued me in
that watir-webdriver does in fact include a method that I thought was
only available in selenium (or selenium webdriver). Instead of doing
a wait_until_present and then doing a click, you can just (globally)
do a
/WebDriver.Timeouts.html
On Sep 27, 6:09 pm, jw joshuawal...@gmail.com wrote:
I have recently switched from a very successful (albeit IE 6-8 only)
Watir suite to watir-webdriver (WW). It has been very painful and
disillusioning but i'm getting close to back where I was 3 weeks
ago.
Of course my reason
ruby 1.8.7 (352)
test-unit (2.3.0)
watir (2.0.1)
watir-webdriver (0.3.3)
IE9/probably others
I don't know if other people have seen this, but I'm occasionally
getting stacks that look like:
C:/Users/jw/.pik/rubies/Ruby-187-p352/lib/ruby/1.8/timeout.rb:64:in
`rbuf_fill': execution expired
That's probably what I would do as well. As a sidenote, if this is
happening on IE, that doesn't mean it will happen in FF. I just had a
popup in FF and (very surprisingly) it seemed the test was still
setting text_fields and clicking buttons in the browser while the
popup was sitting on top of
You're an OSX user, true? So this is happening there as well?
On Sep 17, 5:34 am, Alister Scott alister.sc...@gmail.com wrote:
Thanks SO much for this.
I was experiencing this EXACT same problem yesterday and it was driving me
nuts!
With this patch, will it also work with a newer version of
Successfully tested the above patch on FF6.0.2 on XP. I saw the
'double escaping' patch you/he recommended in your change request but
I'm sticking to this for the time being... works on my machines :)
On Sep 21, 11:54 am, jw joshuawal...@gmail.com wrote:
You're an OSX user, true? So
there.
On Sep 16, 1:19 pm, Mike michaelszor...@gmail.com wrote:
hey jw,
I am running this in irb... sleep/wait shouldn't be an issue there, right?
--
Before posting, please read http://watir.com/support. In short: search before
you ask, be nice.
watir-general@googlegroups.com
http
ruby 187
selenium-webdriver (2.6.0)
watir (2.0.1)
watir-webdriver (0.3.3)
It looks like FF (3.6.6) has some issues with the DL path setting:
browserProfile['browser.download.dir'] = C:\my\new\dir
1) it seems the string you pass must use backslashes and must contain
the drive letter
2) this
Try (as debugging, not as solution) putting a sleep right before the
select. Will let you know if it's a timing issue or an actual 'not found'
issue. You may have to introduce waiting. This is an area that concerns me
: (
--
Before posting, please read http://watir.com/support. In short:
mode, UNLESS the developer toolbar is
open or has been opened/closed in the ie9 session previous to the download.
Very strange. The script times out and the whole ruby process (using
Test::Unit) bombs out (instead of Test::Unit catching the timeout, which is
unfortunate):
C:/Users/jw/.pik
I guess my temporary hack is to very briefly:
#HACK for ie9: open and close dev toolbar real quick
if ($envHash[:browserFlavor]['ie9'])
send_keys(:f12)
sleep 0.1
send_keys(:f12)
end
--
Before posting, please read http://watir.com/support. In short: search before
good one Alister! I usually get taken on this day but everybody at my
office said to expect pranks : )
On Apr 1, 5:23 am, Don Taylor don.tay...@jmedia.com.au wrote:
it would be a pity if all this turned out to be the work of a juvenile few
who treat Watir as their plaything.
just glad
so if you have ahold of the SelectList object using
$b.select_list(:index, 2), can you make if flash? if so, can you view
the values using
$b.select_list(:index, 2).options
The Watir API says options is a method but in my installation it
doesn't seem to be implemented. Here is the code from the
you may have to fire more than one mouse event. i once had to fire an
onmousedown, wait 1 sec, then fire onclick (or something like that, i
don't quite remember). try doing it interactively with irb instead of
writing the test and running over and over. playing with it
interactively sometimes
ok i get it. it's an embed element as opposed to a button or link,
etc.
if you have an IE object you can use the html method to get the html
text. not great but might do the trick
On Feb 9, 6:11 am, ashwin mahesh smashwi...@gmail.com wrote:
There is a chart which shows data in four formats
By having the access right do you mean access as in permissions or
just you're not accessing it correctly?
I have been using enabled_popup and WinClicker to interact with
javascript modal dialogs with decent success.
The button I had to click was labelled Open but the button name I
had to pass to
It seems clear (due to the existence of seleniumGrid) that there's a
need for a standard client/server architecture to cut down on test
runtime, but I never heard about anyone discussing this. WatirGrid
has existed for several months and seems to address this pretty well.
It's not fully fleshed
I think xpath is generally considered a last resort by most people.
To me it seems very brittle. If the layout of your page changes a lot
of your code will break. Using IDs to locate elements is usually your
best choice I believe.
On Jan 27, 12:07 pm, Bharath bkalt...@gmail.com wrote:
Željko,
so it is working (clicking an element) just not the right one?
If the page is static you could try using the index of the element
ie.link(:index, 2)
but this is usually not the best way, especially if your elements have
ids
On Jan 12, 9:27 am, tester86 sagar.am...@gmail.com wrote:
HI
With the
it may be the difference between
http://www.google.com;
and
http://www.google.com/;
if you're typing it by hand each time it's easy to miss that /
On Jan 13, 5:47 am, Chandu80 chandu.she...@gmail.com wrote:
Hi,
When I type in the lines of code as you mentioned,I am able to see the
correct
even I am able to get the text
ie.table(:id, ivr_template:params).div(:index,1).text = lokesh or
ie.table(:id, ivr_template:params)[2][2].text
when you do this
ie.table(:id, ivr_template:params).div(:index,1).text
it's just resolving to a string. you have to get hold of the
text_field
elsif(is_time = self.parseTime(last_value))
should probably be
elsif(is_time == self.parseTime(last_value))
break the problem up, write more helper methods, it's too big to debug
On Jan 12, 3:24 am, Hamid hamid.dela...@gmail.com wrote:
I wonder if anyone can help me to change the cod so it
Did you try all the solutions on
http://wiki.openqa.org/display/WTR/JavaScript+Pop+Ups
solution #3 (after some customization) works for me very consistently.
On Jan 11, 7:29 pm, Alpinweis alpinw...@gmail.com wrote:
I am using the following code taken from Watir Wiki on JS Popups:
def
Thanks to all of you who give your time to make the community strong
and help it grow by helping us newbies!
-josh
On Dec 10, 6:02 pm, Tiffany Fodor tcfo...@comcast.net wrote:
Thanks to Željko and the rest of the Watir team for your confidence in
me. I'm honored to be counted among such a
when poking around at the page, trying to find attributes of UI
elements, it's incredibly useful to open your webpage, start irb, get
a new Watir::IE using attach, then just play around with
puts $ie.buttons[1]
puts $ie.links[12]
etc
On Dec 9, 8:20 pm, Marlon marlonmoja...@gmail.com wrote:
Hi,
Is this intended behavior? The window is invisible, when I look in
Process explorer and try to bring IE's window to front it says no
visible window found.
Oddly, the window becomes visible when calling enabled_popup. This is
about 20 seconds into the test, so it's not window lag and the test is
You probably have tried this, but just in case... you get access
refused when you do
ie.frame(:index,1).text_field(:index,1).flash
but what if you just do
ie.frame(:index,1).exists?
On Nov 28, 1:34 pm, pierrelebai...@gmail.com
pierrelebai...@gmail.com wrote:
I have a script that goes
32 matches
Mail list logo
