Hi,

If I understand your question I had the exact same problem and someone
came to my aid, so I guess it's my turn.

When you get the debugging window for a SUnit assertion failure or
whatever hit the Proceed button.  You will then get another debugging
window for the actual error that should provide all the debugging
facilities you need.

Ken Causey

On Sat, 2003-04-26 at 11:32, Anthony Adachi wrote:
> Hello
> 
..snip..
> Also, I don't understand how one is suppose to examine
> failures in sUnit. When I get a failure the Test
> Runner window displays the failing test. However, the
> description I passed to assert is not listed. When I
> click on one of the listed failing tests a Halt window
> pops-up.
> 
> The closest thing I could find going through the halt
> window was TestRunner>>debugFailureTest:
> Which lists various values (result, details, failures,
> errors, ect.) none of which contain the description I
> passed with the assert message (they only appear to
> list the number of failures). 
> 
> --This is my unit test which expects the string
> 'shouting'.
> ExampleTest>>testShout
> 
> fish := Piexe new.
> self assert: (fish shout) = 'shouting' description: ( 
> 'expected: shouting was:', (fish shout))
> 
> --This is the unit undergoing tests which returns
> 'whisper' as a result of calling shout.
> Piexe >>shout
> 
> shout
> ^'whisper'
> 
> Thanks,
> 
> Anthony