Colin Putney writes:
 >
 > I'd suggest to you, however, that the functionality you describe is not 
 > "missing"  from SUnit, so much as unnecessary. Bringing up a debugger 
 > on the site of a failed assertion or an error is a very efficient way 
 > to find and fix problems. It's even easier to deduce why the test 
 > failed in a debugger, and you can fix it on the spot.

The best way to explain this would probably be to pair...

Bryce