News for hackers. Stuff that matters.
Re:When TDD Fails by shadowfiend on Saturday October 01, 2011 @09:34PM (#3061741)
Which, of course, is part of the point of the article (“I'm not saying TDD is a bad thing, but there are more tests than unit tests, and there are more ways to verify software than testing.“)
Re:When TDD Fails by petercooper on Saturday October 01, 2011 @09:44PM (#3061756)
I think there's some confusion in the definitions which makes things a bit muddier.

TDD is traditionally based around unit tests, but nowadays can pragmatically include integration and functional testing practices. The former definition seems to be the one accepted by the article, but the latter definition somewhat solves most of the problems raised.

Re:When TDD Fails by shadowfiend on Saturday October 01, 2011 @10:24PM (#3061820)
That's absolutely true. Are there any good articles/posts out there on doing test-first with something bigger like integration tests?
Re:When TDD Fails by petercooper on Saturday October 01, 2011 @11:04PM (#3061909)
I don't have any mindblowing articles to hand but this might be a start: http://programmers.stackexchange.com/questions/99735/tdd-is-...

More specifically, the London school of TDD encourages thinking about things from an integration testing level, although you quickly progress to doing unit testing with a ton'o'mocks to flesh out the missing parts.

Re:When TDD Fails by jsdalton on Saturday October 01, 2011 @11:06PM (#3061913)
Check out this thread and the associated article:

http://news.ycombinator.com/item?id=1842582