sUnit in VAST::Debugging a case::how to tearDown correctly

Hi there,

I've recently been using sUnit in VW a lot and am coming back to VAST
and trying to use sUnit as much there.

Apart from the fact that I miss the feaure of the test runner being in
the class browser, I have another question:

When I debug a failing test, I got used to simply resume the test in VW,
and this would call #tearDown as expected. Thus, all my file streams get
closed etc.

In VAST, a failed assertion is not a resumable exception, as far as I
can tell right now. So I can't resume the test after a fail and trust
sUnit to clean up properly.

Do I have to write my tests differently in VAST, in order to be able to
resume a failed #assert:, or are there any settings in sUnit that I can
change?

I am using VAST 7.5.2, if that matters...

Thanx and cu

Joachim

Having taken a second look, I can probably answer my question: there is
an #assert:description:resumable

Well, seems like I need to get used to type a lot more ;-)

This leads me to another question: is there a certain reason for this
difference between VA and VW? Without having dug deeper into VWs sUnit,
it seems #assert: defaults to firing resumabe exceptions, while in VAST
they are not resumable.

Regards

Joachim