Re: Test first as specification

"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?


.

Relevant Pages