On Thu, 9 Aug 2001, Gary Benson wrote: > > On Thu, 9 Aug 2001, Stas Bekman wrote: > > > Some methods of extreme programming suggest writing tests even before > > the code have been written > > I tried this once, for the lexical parser in a desktop calculator program > I wrote. It is a really liberating experience, and leads to greater > experimentation.
the only problem is that usually to write some more advanced tests, you actually need to have some working code, since you have to debug the test itself. So I think that if you have this approach you write only the descriptions of the tests. Is that how you've done this? > If you have tests for everything that can go wrong (this being the > difficult bit), rather than saying "I think this change works: it > doesn't _seem_ to break anything", you merely run the tests over it > and _know_ that it hasn't broken anything. which also saves a *lot* of time! _____________________________________________________________________ Stas Bekman JAm_pH -- Just Another mod_perl Hacker http://stason.org/ mod_perl Guide http://perl.apache.org/guide mailto:[EMAIL PROTECTED] http://apachetoday.com http://eXtropia.com/ http://singlesheaven.com http://perl.apache.org http://perlmonth.com/
