Test driven development
”If you’re a Software Development Manager, ask your engineers if they’re using TDD, and if they’re not, make them start.” Is anyone actually doing this? I mean, lots of people, including me, think it’s a good idea, but who’s actually doing it? Hands up, now!
I am. It’s true, it just works. ;-)
-13621 seconds later
Both the Feed Validator and my Universal Feed Parser are test-driven. The validator was test-driven from day 1; the feed parser had tests added later, but now all new features and bug reports have tests before a single line of code is added.
It’s not for everything, but it’s for more than you think.
36 minutes later
I’ve used it for my own small, personal scripts.
Alas, I haven’t done so at work.
One of the problems with TDD, and Unit Testing in general, is applying it to web applications.
8 hours later
I used it with great success for a university software development project last year. And I’ve gotten my developers at work to the point that they do TDD, but unfortunately not automatic testing … they’re still relying on a QA dept that manually runs tests :-\
45 hours later
I’d echo Mark - it’s not for everything, but it is for most things.
GUIs and web apps tend to be harder (sometimes much harder) than, say, a library, but it’s still be worth trying.
2 days later
Yep, I use it. Joe’s point is well put however - TDD becomes problematic when you are using API’s which are hard to test - web apis being a case in point. It just so happens that APIs written using TDD happen to be easy to test…
6 days later