PyMeld and PyMeldLite (was Re: Separation of content and codefor web)

[Richie Hindle]

Peter,

> Wow, all that and he even writes unit tests!  :-)
> (Out of curiosity: was it test-driven ala TDD, or are these traditional 
> unit tests?)

A bit of both.  These days I'm doing true TDD for almost all Python work.
When I wrote the bulk of PyMeld I wasn't yet converted, so mostly I would
code a feature and then immediately write a unit test.  I've always used
coverage analysis with unit tests, insisting on 100% line coverage
wherever possible (I must get around to releasing my coverage analysis
module some day).  Some of the latterly-added PyMeld features were done
with TDD, and most bugfixes have TDD-written regression tests.

(My smoke-test of the dictionary interface was done with TDD 8-)

In PyMeld's case I've used doctest to do TDD, to very good effect.  Using
the same physical string as the design document, the source code comment,
the API documentation, the unit tests, the regression tests *and* the
website content is just fantastic.

-- 
Richie Hindle
richie at entrian.com