On Apr 20, 4:27 am, bwaybandit lenridge...@gmail.com wrote:
use 'rescue' to handle your exception and there you can pass on
control to your next test or not. use unit/test framework to write
your tests. All that is handled for you.
But do be aware that by design with most of these
Hi Durgesh!
Are you using the Test::Unit assertions?
Originally, I used the Test::Unit assertions, but moved to the Watir
assertions for this reason. Watir assertions won't cause the script
to stop - it will keep running until it can't find any of the page
objects to continue your tests.
You
To clarify, Tiffany is talking about the verify method that is part of
the Watir assertions.
Bret
Tiffany Fodor wrote:
Hi Durgesh!
Are you using the Test::Unit assertions?
Originally, I used the Test::Unit assertions, but moved to the Watir
assertions for this reason. Watir assertions
where is that documented? I didn't even know we had that method (I
went and wrote my own verify for the first generation of my
automation)
On Apr 20, 4:07 pm, Bret Pettichord b...@pettichord.com wrote:
To clarify, Tiffany is talking about the verify method that is part of
the Watir
http://groups.google.com/group/watir-general/browse_thread/thread/df7eca6a7a591e05
http://wtr.rubyforge.org/rdoc/classes/Watir/Assertions.html
Chuck van der Linden wrote:
where is that documented? I didn't even know we had that method (I
went and wrote my own verify for the first