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.

Required fields*

3
  • As I said before, it was a simple scenario, just to learn about TDD and Mock objects... A great answer, thank you. And what about UML? Should I avoid it? Commented Jan 24, 2011 at 13:37
  • @thomas, no need to avoid UML, it does not conflict with TDD. UML is very good for visualizing / communicating design issues. This can be extremely useful at certain development stages. However, design evolves, and trying to keep a beautiful and detailed UML system diagram in sync with the code can quickly become a burden. So remember to throw it away when you don't need it anymore :-) Commented Jan 24, 2011 at 13:42
  • 1
    @thomas, btw the convention here is to upvote answers you find useful, by clicking on the up arrow next to the answer :-) Commented Jan 24, 2011 at 13:49