On 6 Aug 2006, at 14:27, Sagar Shah wrote:
[snip]
No, I think you're absolutely right. I've also long held the view
that
functional tests provide a better cost:benefit return.
Unit tests do have their advantages, but if I had to chose between
writing unit & functional tests (say because of resource constraints)
I'd definitely go for writing functional tests.
[snip]
Obviously - both is best ;-)
If I've already great steaming lump of untested code, I'd agree with
you completely. Functional tests will usually give you much more bang
for your buck.
I gotta admit though... if I'm writing fresh code, and I /had/ to
pick between TDD produced unit tests and functional/acceptance/
customer tests, I'd pick the TDD produced unit tests every time.
My experience has been that programmer driven TDD produced tests will
cut development/debugging time and produces more robust code, where
you can spend a lot of time flailing around if all you have is
automated functional tests.
As ever YMMV.
Cheers,
Adrian
