SUnit, formerly known as Testing Framework is Kent Beck's framework for automating Programmer Test s in Smalltalk Language programs.
The Smalltalk version of the Testing Framework can be downloaded from
http://sunit.sourceforge.net/
Version 3.1 (2003) supports
Object Studio 6.8
Smalltalk/X 4
(With Release 2 the software is called SUnit.)
Original documentation is available at
www.xprogramming.com 
Simple Smalltalk Testing: With Patterns Kent Beck, and
Chapter 30 "Simple Smalltalk Testing", in Kent Beck's Guide to Better Smalltalk by Kent Beck, Donald G. Firesmith (Editor), Cambridge University Press, December 1998, ISBN 9780521644372
Note that the Test Suite class>>named: method is not supported in 2.3 (and beyond?)
SUnit is included in the main distributions of Squeak 3.9, Squeak 3.10 and Pharo 0.1 Source packages can be downloaded from Squeak Map for Squeak versions 3.8 and earlier.
I wrote a simple VA Smalltalk front end to the framework, following Kent's suggestions. I'll be happy to pass it on to anyone who'd like to use or expand on it. -Joseph Pelrine
See Enhancing Sunit
Is there a good pattern for placing tests in ENVY applications? Should my application pre-req SUnitApp, or should I create an Test App that prereqs the real app and the SUnitApp (I think the latter). - Steve Cline You sure want the latter as you don't want to pre-req SUnit in a runtime image- Daniel Enting
It seems, version 2.6 doesn't work well with name spaces, at least in Visual Works 5i.1b. It doesn't find classes in namespaces below Smalltalk. I have submitted a test case and fix to Samuel Shuster, the current maintainer. Meanwhile, if you need it, contact me. --Hasko Heinecke
Shouldn't it be named Small Unit?
See also Jeffrey Odell 's SUnitBrowser at www.odellsoft.com
I'm using the SUnit extensions for the Refactoring Browser. I'm starting to really hate the poor design of the interface.
There's a Debug button and a Run button. If you hit the run button, it suppresses any walkbacks. If you hit run and you get an error or failure which you wish to inspect, hitting debug afterwards will run the test all over again. This isn't any fun when your one measly test takes upwards of 5 minutes to run.
So if I've only got one test selected, for what possible reason am I allowed to use the run button? I can't conceive of a legitimate reason why I would wish to do such a thing.
See original on c2.com