SUnit stack traces when a test fails
Andrew P. Black
black at cse.ogi.edu
Tue Nov 12 18:47:23 UTC 2002
At OOPSLA DesignFest, we practiced some-test first programming using
Sunit in Squeak 3.2
When there was an error in the test, the walkback that one obtained
by clicking the the testRunner was as one would expect -- the message
not understood or whatever that caused the error.
However, once I had gotten rid of all the errors, and the test
actually failed (i.e., I asserted something that was not true) I was
not getting a useful walkback from the testrunner. It looked as
though I was getting a stack trace on part of the testrunner
framework itself, rather than on the failing assert.
I ended up putting "self halt"s in the tests to get into the debugger
at the right point.
I'm not sure how to debug this. Have others seen this behaviour too?
Or have I done something weird with my image?
Andrew
More information about the Squeak-dev
mailing list
|