Pros and Cons and of using an Auto Mocking container in your tests

My blog has moved. You can view this post at the following address: http://www.osherove.com/blog/2008/4/25/pros-and-cons-and-of-using-an-auto-mocking-container-in-your.html
Published Friday, April 25, 2008 11:54 AM by RoyOsherove

Comments

Friday, April 25, 2008 12:28 PM by DotNetKicks.com

# Pros and Cons of using an Auto Mocking container

You've been kicked (a good thing) - Trackback from DotNetKicks.com

# Access Your Auto » Calgary Police Concerned About Grand TheftAutoIV

Pingback from  Access Your Auto » Calgary Police Concerned About Grand TheftAutoIV

Friday, April 25, 2008 2:48 PM by Jason

# re: Pros and Cons and of using an Auto Mocking container in your tests

Scott Belware argument at ALT.NET Seattle was that because an AMC makes testing less painful it can hide code smells.

Thursday, May 08, 2008 8:36 AM by Ishitori

# re: Pros and Cons and of using an Auto Mocking container in your tests

What I find bad in automock style is that you are now not obliged to make your code less coupled. If you have a tool such as TypeMock you can mock almost everything without rewriting your code at all.

But if you had to write all mocks manually you would probably try to reduce the amount of work and try write modules less dependable from others using interfaces, dependency injections and IoC patterns.

Though I read somewhere an article named like "Don't code for testability", but as everywhere it is better to try find a golden middle.