To me, developers that are not applying TDD practices during their day-to-day job always seem […]
AutoTest.NET
I just want to quickly point out a tool that I?ve been playing with for […]
Boxcar Case Macro in Visual Studio 2010 – Video
I get so much use out of this handy dandy little macro that I just […]
An Evolution of Test-Specification Styles – My Journey to MSpec
Over the last few years, the practice of Test-Driven Design and Behavior-Driven Design has increased […]
Note to self: Asp.Net MVC Controllers are not Code Behind
Sometimes I think things are more complicated than they really are. I got my head […]
Unity/Moq – AutoMocker or AutoMockingContainer
What is an Auto Mocking Container? This post started to get a little long, so […]
StatLight – Goes Open Source
Although I made a very minor attempt at making StatLight a “for-sale” product, I knew […]
Wrapping up the StructureMap Automocking Container
UPDATE: I apologize…the original wrapper did not allow injected dependencies. I have fixed this bug and updated the sample.
I have been using StructureMap.AutoMocking with MSpec (Machine.Specifications) and Rhino.Mocks for a few months now. Although I am very comfortable with the patterns that emerge from using the frameworks together, introducing StructureMap.Automocking to other developers is sometimes challenging. I decided to wrap the details of the container to make the intention clearer and explanation easier. I have started using this wrapper in my projects, and have found it makes building up specifications more efficient in my daily coding.