Re: Test first as specification

On Fri, 5 Aug 2005 22:58:10 +1200, "Lurker" <nowhere@xxxxxxxxxxx>
wrote:

>"Robert C. Martin" <unclebob@xxxxxxxxxxxxxxxx> wrote in message
>news:mu43f1h31fvvh9fcmhrl3jvffiruuqe6bd@xxxxxxxxxx
>
>> You convert the spec into tests and apply those tests (whether manually
>> or automatically, but hopefully automatically). This means that there is
>> a mapping of tests to specs, and specs back to tests. So specs *are*
>> tests, and tests *are* specs.
>
>Let's take your typical syntax diagram for a programming language.
>Given that, it's rather easy to write tests which validate that some
>implementation passes those tests (note that it doesn't prove that the
>implementation actually matches the specs - only that it passes your
>tests). But that aside, how would you go with TDD first to come up
>with that syntax diagram?

One syntax element at a time.


-----
Robert C. Martin (Uncle Bob) | email: unclebob@xxxxxxxxxxxxxxxx
Object Mentor Inc. | blog: www.butunclebob.com
The Agile Transition Experts | web: www.objectmentor.com
800-338-6716


"The aim of science is not to open the door to infinite wisdom,
but to set a limit to infinite error."
-- Bertolt Brecht, Life of Galileo
.