Okey, I've finally found the culprit of my failing tests.
I don't know exactly, what has changed in Watir to make my tests to
fail, but I know that it is not Watir's fault per se.
I also changed subject of this topic, because original problem is not
related with this seem-to-be-greater problem.
As I've stated already on my previous post, I already diffed wait
method and only difference was one additional rescue NoMethodError.
But my problem is not related with that fix, because I'm not receiving
any NoMethodErrors. I still guess that the logic may be behind the
fact that 1.6.2 is
Release notes (http://wiki.openqa.org/display/WTR/Release+Notes) from
1.5.6 to 1.6.2 doesn't seem to mention anything regarding wait method
or wait logics.
I also diffed methods click, click!, click_no_wait, fire_event and
wait from 1.5.6 and 1.6.2 and they were exactly the same (one
difference
My question was, why my tests started to fail? Also, fire_event seems
to behave differently, e.g. it will return before actual event has
been finished. With 1.5.6 this seemed to work well enough - it didn't
carry on before fire_event was actually finished.
Is just Watir 1.6.2 made seemingly
this works in 1.6.2
you might want to use wait_until and make sure your object shows up
before you use select
On Apr 2, 4:38 am, Jarmo Pertman jarm...@gmail.com wrote:
Hello.
I've updated Watir from 1.5.6 to 1.6.2 and at least one test started
failing with suspicious problems.
First, I
