3 ms·
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
by shadowfiend 15y ago
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.“)
- petercooper 15y agoI 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.
- shadowfiend 15y agoThat's absolutely true. Are there any good articles/posts out there on doing test-first with something bigger like integration tests?
- petercooper 15y agoI don't have any mindblowing articles to hand but this might be a start: http://programmers.stackexchange.com/questions/99735/tdd-is-it-just-about-unit-tests 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.
- jsdalton 15y agoCheck out this thread and the associated article: http://news.ycombinator.com/item?id=1842582 http://news.ycombinator.com/item?id=1842582