[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Suggestion] GNUstep-test for quality control (WAS: Re: deferreddeal
From: |
Chris Hanson |
Subject: |
Re: [Suggestion] GNUstep-test for quality control (WAS: Re: deferreddeallocation) |
Date: |
Fri, 17 Oct 2003 16:50:36 -0500 |
On Thursday, October 16, 2003, at 12:11 PM, Pete French wrote:
When implementing a feature, you first write a simple test case for
one
aspect of that feature. Build, the test suite runs including your new
Out of interest, how do you test the testing code ? Havent you just
moved the problem to a different bit of code ?
No. The testing code is typically so simple that it's very clear
whether or not it's correct. See the C2 wiki for more details:
http://c2.com/cgi/wiki?TestDrivenDevelopment
As the wiki describes, the standard book on how to do test-driven
development is "Test-Driven Development" by Kent Beck, co-creator of
JUnit. It's short and sweet and definitely worth a read.
-- Chris
--
Chris Hanson, bDistributed.com, Inc. | Email: cmh@bDistributed.com
Custom Mac OS X Development | Phone: +1-847-372-3955
http://bdistributed.com/ | Fax: +1-847-589-3738
http://bdistributed.com/Articles/ | Personal Email: cmh@mac.com