Here are some other suggestions:
1) Perhaps try adding messages to your asserts. If you just want some
extra logging when failures occur, this may be all you need to do.
All the assert methods I've seen support this; just add the message as
the last arg you pass to the assert call.
The message
Whoops, my verify example was meant to be more like this:
test_testMethodFoo
result = $ie.link(:text, nameOfLink).exists?
verify(result)
puts Test is still executing...
if !result
do_some_extra_stuff()
end
end
___
Wtr-general mailing list
I just want to make assert of link, after i remove rescue block, assert method works and I can see that test failed on report, but it skips my test case and I wish to avoid it, I want to add some extra information to my logger file when test fails
def test_namemethod begin assert($ie.link(:text,
I answer myself I've done something like this:beginassert($ie.link(:text, 'name_of_link').exists?)rescue =e#my extra code to do something when assert failed, then i return exceptionraiseend
now it seems to work, does anyone know better way?Luke
___
Luke wrote:
now it seems to work, does anyone know better way?
Use the verify method that i've posted to this mailing list and which is
included in 1.5.1.1100
Bret
___
Wtr-general mailing list
Wtr-general@rubyforge.org
the problem is that when I put 'rescue=e' statement I catch exception
and report shows that test pass
If you rescue the exception is it not swallowed up?
do you then not need to invoke the exception message and the stacktrace?
rescue = e
p e.message
p e.backtrace
and then
Are you using Test::Unit::Reporter? It could be useful to put
together a small demo script that will demonstrate the problem.
So it sounds like you have a test that is expected to fail, and it's
not failing? (Or is it that the script is behaving properly, but the
report does not have the
