> > How would you define the behavior of a web-browser as a > > series of tests? How about even just a SAX parser? Do > > you really think it would be easier to understand what > is > > required of a program if all you were given were a set > of > > tests to run? > > I'd be a lot more confident to build something close to > what is expected if I were given tests instead of a > requirements document with the usual ambivalence. There > e would also be a lot less discussion about correctness > and interpretation. Either the tests pass or they fail.
The problem is in most cases the people defining requirements would never be able to create workable tests, so the need for requirements documentation doesn't go away.
Previous Topic
