Jim Weirich <jweirich / one.net> writes:

> On Mon, 2003-06-02 at 07:24, John Johnson wrote:
> > The time has come. I'm tired of that unsure feeling when I'm about to
> > release a program. So I've decided to jump on the unit testing band-wagon.
> > Trouble is, the wagon is going a little fast for me, and I'm kinda' hanging
> > off the back end of it.
> 
> The best way to learn about unit testing is to ...  do unit testing. 
> Your first attempts will feel awkard, but you will improve with time.
> 
> There are several ways to approach unit tests.  You didn't mention a
> particular technique, but I would recommend the "test-first" approach
> where you write your unit test before the production code.  If you
> follow the rule that you never add new functionality to a program
> without a broken unit test, and then only write enough code to make the
> test pass, then you get excellent test coverage with a small investment
> of time (that pays for itself many times over).
> 
> If you are not familiar with the "test-first" approach, there are a
> number of writeups on any of the web sites devoted to XP (Extreme
> Programming).

There's a nice book online available at
http://groups.yahoo.com/group/testdrivendevelopment/files/

just my .02
frank

-- 
Frank Schmitt 
4SC AG		phone: +49 89 700763-0
		e-mail: frank DOT schmitt AT 4sc DOT com