Skip to main content

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.

4
  • I pulled down Enterprise Library 5.0 and had a look at the source code. It does have an extensive collection of tests, but there's a lot of test fixture, call handler and other complex objects in the test project; it seems almost like an application in its own right. While I admire the work, I don't see how it fits into the TDD world view of red-green-refactor. Commented Nov 26, 2010 at 23:42
  • @Robert - I can only tell you what they told me... They used TDD when writing it. Commented Nov 27, 2010 at 13:22
  • 6
    @Robert - It is not unusual for the test suite to take on a life of its own. DRY applies to both your application and the tests. In TDD you are only ever doing 1 of 4 things: Writing tests, writing code, refactoring tests, refactoring code. If you are doing all of these things in a red-green-refactor pattern, then you are doing TDD. Commented Nov 27, 2010 at 18:55
  • 1
    @Jeff: Thanks for clarifying that. I think there are some differences between the way TDD is explained (in reductionist, mechanistic terms), and the way it is actually used in real-world scenarios. Commented Nov 27, 2010 at 19:08