Story Test Driven Development

Description

StoryTestDrivenDevelopment says "Write new code only if an automated storytest has failed." We do this to maximize our understanding of requirements, produce executable documentation and focus our design on only what's absolutely needed.

StoryTestDrivenDevelopment includes the practices of UnitTestDrivenDevelopment, Refactoring and DomainDrivenDesign.

The flow tends to go like this: customers write a failing storytest and check it in to a source repository, developers then work to make the storytest pass. Their work will often include doing UnitTestDrivenDevelopment as they work to define or refine domain objects. Refactoring happens at all levels within this process.

-- JoshuaKerievsky - 12 May 2004