Is Typemock too powerful? Will it kill design for testability?

TDD in SharePoint - Using Dependency Injection | Agile Sharepoint development by 21apps and Andrew Woodward MVP

Wed, 07 Jan 2009 23:01:28 GMT

Pingback from TDD in SharePoint - Using Dependency Injection | Agile Sharepoint development by 21apps and Andrew Woodward MVP

Unit testing part 3: Design for testability « Freekshow

Unit testing part 3: Design for testability « Freekshow — Wed, 03 Sep 2008 11:20:54 GMT

Pingback from Unit testing part 3: Design for testability « Freekshow

MSDN Blog Postings » Typemock

MSDN Blog Postings » Typemock — Tue, 04 Mar 2008 13:47:08 GMT

Pingback from MSDN Blog Postings » Typemock

Typemock

Noticias externas — Tue, 04 Mar 2008 12:51:54 GMT

Roy recently posted his thoughts on Typemock - whether it's too powerful and will kill TDD. His conclusion

Typemock

ploeh blog — Tue, 04 Mar 2008 12:46:36 GMT

Roy recently posted his thoughts on Typemock - whether it's too powerful and will kill TDD. His conclusion

Testing Theories Part 4 - TypeMock Isolator - The Dark Horse of Unit Testing?

Alec Lazarescu's Blog — Tue, 19 Feb 2008 05:13:11 GMT

A lot has been discussed on the pro's/con's of IoC for the purposes of unit testing and in general it

Será Testar O Nosso Objectivo Final?

Paulo Morgado — Sun, 03 Feb 2008 17:58:44 GMT

Na minha opinião, os habituais defensores de TDD equiparam-se a são fanáticos religiosos que pensam que

The Case For Typemock

ISerializable - Roy Osherove's Blog — Sun, 20 Jan 2008 23:00:05 GMT

I just wrote an email to someone regarding Typemock . We were discussing why they don't think Typemock

re: Is Typemock too powerful? Will it kill design for testability?

Eric — Fri, 18 Jan 2008 16:54:47 GMT

The real compelling argument for TypeMock is the legacy code argument. When I starting a new project, I would probably pick Rhino.

For me, this is about using the right tool for the right job. For new development, I find RhinoMocks to be the right tool. But, I've done enough with legacy code to know that having the functionality that TypeMock provides is very useful when working against someone else's libraries that were obviously not written with testability in mind.

re: Is Typemock too powerful? Will it kill design for testability?

Joe Brinkman — Fri, 18 Jan 2008 10:34:25 GMT

I love this quote "lose sight of design decisions about making the code testable in the first place". To me this sums up what I perceive as a huge problem with many people in the current Agile/XP world: creating testable code is a means to an end, it is not the ultimate goal. The easier it is to create testable code (because the testing tools are better), then I have more freedom to choose the best design to solve the business problem, instead of trying to find the best design to solve the testing problem. The two concepts are not the same.