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 is missing or (b) the missing element is an application bug and should fail immediately.
It'd be useful if the waiting page on the web site could separate a bit between the two approaches. Combining them is not always pleasant, see e.g. https://groups.google.com/forum/#!topic/selenium-developers/91vSZHxAnCg Jari On Wed, Oct 5, 2011 at 1:27 PM, Alister Scott <alister.sc...@gmail.com>wrote: > I am glad you found it useful. I have put it on the watirwebdriver.comsite: > 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-general+unsubscr...@googlegroups.com > -- 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-general+unsubscr...@googlegroups.com
