Stories
Slash Boxes
Comments

NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

use Perl

All the Perl that's Practical to Extract and Report

Test Driven Development More | Login | Reply

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Without JavaScript enabled, you might want to use the classic discussion system instead. If you login, you can remember this preference.

Specification- and Test-Driven Development (Score:1)

by kid51 (5328)

I stubbed out the module using module-starter and wrote the POD. Writing the API documentation first had the nice effect of keeping it simple. ...
Several years ago I gave a talk to New Orleans Perlmongers on writing a module in the CPAN style. As a gag, I said, "First you write your documentation, then you write your tests, and only then do you write your code."
It was a gag then, but over the next couple of years I began to wonder, "What if I really did write my documentation first?" I.e., what if I
- Re:Specification- and Test-Driven Development (Score:1)
  
  by zby (4817) on 2009.07.28 15:28 (#69734) Homepage
  
  I've made a list of online resources on API design [blogspot.com] - I think all of them advice writing APIs and example code using that API before writing implementation.
  
  Reply to This
  
  Parent

Get More Comments

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.