Efficient python programming...

[Sean 'Shaleh' Perry]

> 
> I disagree, if the tests are written first (and run, proving that
> they will fail when the code is wrong or missing).
> 
> The tests are executable requirement specifications.  Running
> them "proves" (yes, not 100%... nothing could) that the code
> meets the specs.  The specs could be wrong of course, but that
> doesn't mean the code is broken...
> 

this also assumes the test covers every possible failure.  this also assumes
one can write tests for that section of code.