[TIP] testing: why bother?

Kumar McMillan kumar.mcmillan at gmail.com
Wed Mar 23 10:01:50 PDT 2011

On Wed, Mar 23, 2011 at 11:32 AM, Michael Foord
<michael at voidspace.org.uk> wrote:
>> I have tried TDD but it feels more natural for me to commence most
>> *new* projects or *hard* problems with a prototyping phase where I
>> hack code without any tests just to get it to work.  Afterwards, I
>> usually throw away a lot of that code and rewrite/restructure using a
>> TDD approach.  For small changes, bug fixes, or easy problems I always
>> use TDD.  The prototyping phase is risky but it's faster, easier, and
>> less wasteful (for example, you don't have irrelevant tests laying
>> around).
> That process is incorporated within classic TDD and is called "spiking"
> (experimental or exploratory changes where testing is inappropriate because
> you don't know *what* to test).

Sweet.  I knew I was smart.

> Michael
>> Kumar
>> _______________________________________________
>> testing-in-python mailing list
>> testing-in-python at lists.idyll.org
>> http://lists.idyll.org/listinfo/testing-in-python
> --
> http://www.voidspace.org.uk/
> May you do good and not evil
> May you find forgiveness for yourself and forgive others
> May you share freely, never taking more than you give.
> -- the sqlite blessing http://www.sqlite.org/different.html

More information about the testing-in-python mailing list