FreeLists / openbeos / [openbeos] Re: I know I'll get flamed for this but....

["Erik Jakowatz" <erik@xxxxxxxxxxxxxx>]

Not to put too fine a point on it, but unit tests are the shiznit. =)  
Seriously, folks, unit tests are not difficult to write -- once you've 
figured out what to test and how.  I would submit that if you don't know 
"what to test and how" for a particular bit of functionality you're 
working on, you don't really know what you're doing. =)  Since the code 
coming in seems to be of good quality, I can only chalk up any lack of 
unit tests to sheer laziness. ;)  The great thing about have a full set 
of unit tests in place is that you know *immediately* if something has 
been broken.  When a bug is found, you drop a test in for that bug and 
you will never have to fear that it might creep back in unnoticed.  And 
there's nothing like running your test suite and seeing everything pass.

e

>:-) I am a big XP freak. :-)
>I just can't figure out how to convince developers who are working in 
their
>spare time to write unit tests. :-/
>I don't have a money stick to beat people with. :-)
>My next idea was to try to have the people who are new to BeOS write
>unit tests, since they need nothing more than the BeBook and a copy of
>BeOS. Several people have volunteered. No one has come back to 
>me with test code, yet. :-/

Data is not information, and information is not knowledge: knowledge is 
not understanding, and understanding is not wisdom.
        - Philip Adams