Re: Test first as specification

"Robert C. Martin" <unclebob@xxxxxxxxxxxxxxxx> wrote in message
news:vf0dd1tp1evjjmm3b5a2t16g3efuck2d0e@xxxxxxxxxx
>
> You should specify the requirements in terms of automated
> acceptance tests (e.g. take a look at fitnesse.org). The
> developers (in india) should write the unit tests, and make
> all the tests pass.

Just a bit of an off-topic quibble. While I cannot disagree with the notion
of acceptance tests as specifications, sometimes they are not, and cannot
be, exactly equivalent to requirements. For details, see:

http://cauvin.blogspot.com/2005/07/should-all-requirements-be-testable.html

--
Roger L. Cauvin
nospam_roger@xxxxxxxxxx (omit the "nospam_" part)
Cauvin, Inc.
Product Management / Market Research
http://www.cauvin-inc.com


.