Yes, it should. Can you provide a reduced example where that's not the case?
Den 5. okt. 2011 kl. 21:50 skrev Abe Heward :
Hey guys,
I'm using watir-webdriver (0.3.3) and Test::Unit.
In my code I'm trying to validate that an object is NOT present on the
page...
assert_equal(false, @browser.but
Hey guys,
I'm using watir-webdriver (0.3.3) and Test::Unit.
In my code I'm trying to validate that an object is NOT present on the
page...
assert_equal(false, @browser.button(:id=>"post").exist?)
...However, instead of getting the "false" result for the .exist?,
apparently it's throwing this
On Wed, Oct 5, 2011 at 4:08 PM, Rahul Sharma wrote:
> Hi Jari,
>
> We have been using explicit waits for a long time and one drawback that we
> have encountered is when the tests fail. The timeout I believe with
> Watir::Wait.until is 30 secs. If the test was going to fail it will still
> try to l
OK. I just found a thread relating to this issue. Don't know if it's been
resolved. Seems like an issue with firefox. Did you try on any other browser?
Here is the thread
http://code.google.com/p/selenium/issues/detail?id=157
On 5 Oct 2011, at 19:29, Cristina Dumitrescu wrote:
> I have attached
OK. I can't see this text field :
>
> $browser.text_field(:class => "macXfunc", :id => "macjumpbox")
Where is it on the page??
On 5 Oct 2011, at 19:09, Cristina Dumitrescu wrote:
> Because of that I cannot do any progress. The way to edit something is just
> to use that jump box.
>
> Thanks
Because of that I cannot do any progress. The way to edit something is just
to use that jump box.
Thanks a lot in advance,
Cristina
On Wed, Oct 5, 2011 at 12:06 PM, Cristina Dumitrescu <
cristina.watir.toro...@gmail.com> wrote:
> Hi,
>
>
> I do not know why is not working on that particular e
Hi,
I do not know why is not working on that particular element.
just save the following code into a ruby file and run it.
#-
#firefox
#--
prof = Selenium::WebDriver::Firefox::Prof
Hi Jari,
We have been using explicit waits for a long time and one drawback that we
have encountered is when the tests fail. The timeout I believe with
Watir::Wait.until is 30 secs. If the test was going to fail it will still
try to locate the element(correct me if I am wrong!). Should this be cut
Very good thank you for posting this!
On Tue, Oct 4, 2011 at 3:36 PM, jw wrote:
> 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
>
Hi,
I am trying to handle modal dialog with FireWatir. I am using the
FireWatir-1.8.0 version. When i use the command
ff.modal_dialog(:title,'Program Management') then it displaying the
error message : undefined method 'modal_dialog' for FireWatir.
--
Before posting, please read http://watir.com
I usually prefer waiting explicitly (especially since watir-webdriver makes
it so easy) and never use implicit waits. Implicit waits hide information
about app behaviour from test developers that I think is often quite
relevant, and slows down your tests when (a) you want to check that an
element i
I am glad you found it useful. I have put it on the watirwebdriver.com site:
http://watirwebdriver.com/waiting/
--
Before posting, please read http://watir.com/support. In short: search before
you ask, be nice.
watir-general@googlegroups.com
http://groups.google.com/group/watir-general
watir-g
after you create a browser, simply set the wait:
require 'watir-webdriver'
b = Watir::Browser.new
b.driver.manage.timeouts.implicit_wait=3
It will wait *up to* 3 seconds before complaining it can't find the element.
If it finds it immediately, there is no wait.
Alister
--
Before posting, ple
Hi Joshua,
Can you please tell where exactly this implicit wait can be defined? Would
you put this in the environment file? Also, I am currently using as you
mentioned quite a lot of Watir::Wait.until{...} and wait_until_present in my
scripts. Does this implicit wait value helps trying for 3 secon
14 matches
Mail list logo