Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

7
  • 3
    Benefit point 2 can be achieved with simple unit tests without a TDD approach as well. Benefit 1 you should be doing anyhow. (Focusing on the API) It's still entirely possible to create a crappy API using TDD, but yes, you are guaranteed that it will work (for the written tests). Commented Aug 4, 2011 at 12:34
  • 2
    The question was not asking about the benefits of TDD. There are already plenty of other questions on that. Commented Aug 4, 2011 at 13:18
  • 1
    @aaronaught, I am addressing his pain points. Commented Aug 4, 2011 at 15:05
  • Answers should address the question. Commented Aug 4, 2011 at 15:09
  • 1
    @aaronaught, then write some of those. Commented Aug 5, 2011 at 0:10