[This post is in response to a post (actually a couple posts) that Roy Osherove has recently posted on TypeMock... go read it first].
Roy is hitting right into what I was trying to say all those years on CodeBetter when I was "battling" a few of my then co-bloggers. It's the dogmatic aspects of TDD that scare many of us.
Not only that one has to do TDD, but to do it as a "way to a better architecture" which implies that "thou shalt always use pattern x." I have argued many times over... what if what I'm doing is fairly trivial or there is no need for a large architecture (yet).
Roy's post is a defense of TypeMock, but in the midst of talking about it's ability to lure non-agilist's over he makes this statement (copied directly from his blog):
agile is about embracing what works for a particular team...
That's sounds like a very GRDD (Git 'R Done Dev) statement...
As a (for the most part) non-agilist have gravitated to MbUnit as a unit-testing framework (I still test after design). MbUnit appears to be extremely pragmatic and extensible which is what I need.
I have looked at the mocking frameworks, but the fact that they impose certain tenets of the TDD faith (AKA imposed patterns that are ALWAYS used to make things more "testable"), I have yet to use any of them. I just installed TypeMock, and will be using it soon...
| posted on Tuesday, January 22, 2008 10:23 AM