Hi!
If you know which elements are likely to be missing, you could add a
verification that the element exists, which would trigger a failure if
it's missing and then add a conditional to act on it. A Test::Unit
example would be:
verify((ie.link(:text, 'My Link').exists?), message='My Link
You could do it a couple of ways.
1. Use an if/else statement (as seen here -
http://wiki.openqa.org/display/WTR/Example+Logging)
if condition=true
# log pass
else
# log fail
end
2. Use the Exception class:
Here's the basic syntax:
begin
# do something
rescue
# log the failure if
Hi
I have been using if/else statements in my scripts but I was just
wondering if there was other ways that I could handle exceptions.
Thanks for your help.
On Feb 4, 12:03 pm, orde ohil...@gmail.com wrote:
You could do it a couple of ways.
1. Use an if/else statement (as seen here
I'm able to use begin/rescue/end for 99% of cases. Normally I'll
collect the error into an array for logging or an email report
afterward. Using those conventions, the script never stops, and I
don't have to be glued to the console to find out when it breaks.
On Feb 4, 1:42 pm, tester86
