>first the developer writes a failing automated test case that defines a desired improvement or new function If you TDD at the highest level that makes sense,

>first the developer writes a failing automated test case that defines a desired improvement or new function If you TDD at the highest level that makes sense, with a test that mirrors the requirements in the form of a user story rather than the implementation (e.g. of a new function) most of the comments in this article dont really make sense. Yes, if youre not sure about requirements its too early to write the test, but it's also far too early to be writing any production code. There arent any real benefits to test-after. The risks of writing a test that mirror an implementation are higher. The risk of undertesting is higher. And, I've also noticed that people who are very thorough with test-after tend to over test.