Comments on: Auto mocking Explained

By: Alexander M. Batishchev

Alexander M. Batishchev — Sun, 07 Aug 2011 18:26:00 +0000

That was great. Thank you.
Just one bummer you to know: code highlighting doesn’t fit into window’s width

By: Brian

Brian — Fri, 06 Feb 2009 23:42:17 +0000

The one thing I have to say that auto-mocking does to the negative, and IoC in general, is for new people coming in there is a lot of ‘magic’ that they have to figure out that they have no tests to look to for guidance and have been simply stuck going through individual classes and going ‘oh…there an overloaded constructor with a different/second argument type).

Not saying I disagree, just saying that’s one of the problems I’ve seen people have, most I’ve worked with want to ‘see it work’.

By: Joshua Flanagan

Joshua Flanagan — Thu, 05 Feb 2009 01:39:12 +0000

@Michael – it could be. But I’m comfortable assuming that any truly worrisome design smell will expose itself in a more impactful way than the automocker could disguise.

By: Joshua Flanagan

Joshua Flanagan — Thu, 05 Feb 2009 01:35:07 +0000

@David – I can’t speak for the Windsor-based AutoMockingContainer. The StructureMap RhinoAutomocker always creates mocks using the DynamicMock() method. If you need a specific fake to be a stub or static mock, you can manually create it and then use the Inject() method on the automocker so it knows to use it (works for concrete classes as well).

By: Joshua Flanagan

Joshua Flanagan — Thu, 05 Feb 2009 01:25:44 +0000

@Jake – I couldn’t say if AutoMocking is one of the barrier words that Scott was referring to. But I don’t think it matters in the context of this post, as I had a different target audience in mind than what he was referring to. I targeted developers who are already familiar with, and using a mocking framework, but a little skeptical of automocking.

By: Joshua Flanagan

Joshua Flanagan — Thu, 05 Feb 2009 01:21:35 +0000

@chrissie1 Yes, this information will get into the StructureMap documentation (eventually…)

By: Michael Hedgpeth

Michael Hedgpeth — Wed, 04 Feb 2009 13:19:35 +0000

I do think this is cool, but…

Could it be your desire for automocking is covering up the need for a better design? Maybe in this case you should rethink your dependencies.

By: Chris Allen

Chris Allen — Wed, 04 Feb 2009 11:20:59 +0000

Awesome, I’ve been looking for more information on this for a while now. Thanks for the info.

By: David

David — Wed, 04 Feb 2009 09:05:44 +0000

Awesome post. Thanks for this!

Quick question: how do you handle injecting mocks vs. stubs using automocking? Or do you always use stubs and override where necessary?

By: Łukasz Podolak

Łukasz Podolak — Wed, 04 Feb 2009 09:02:29 +0000

Excellent article, thank you for a great explanation.