« Perforce: Why do you make simple things hard?
Goats, goats and more goats in Seattle »

Designing for Testability: 14 facets of TypeMock.NET

There has been much talk about Designing for Testability lately. Basically the argument is:

Should our Tests (Enabling Mock Insersions) Drive our design? or should we use tools to do it for us?

From: 14 facets of TypeMock.NET and Designing for Testability

The author of TypeMock.NET has started blogging and has compiled a great collections of views from people who are debating using, against, or in favor of mock tools.

This entry was posted on Wednesday, September 27th, 2006 at 11:53 am and is filed under Code, LinkBlog, Mock Objects, Testing. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

One Response to “Designing for Testability: 14 facets of TypeMock.NET”

  1. […] Designing for Testability: 14 facets of TypeMock.NET […]

Leave a Reply