I just want to quickly point out a tool that I?ve been playing with for […]
If Self-Documenting Code is the What, Unit Tests are the Why
It is not enough to just write code that is clean and self-documenting.? Eliminating comments […]
Behaviors with MSpec
In my previous posts, I showed the syntax for context/specifications using Machine.Specifications (or MSpec for […]
MSpec and Auto Mocking
In my previous post, I explained how to get started with Machine.Specifications (or MSpec for […]
Getting Started With Machine.Specifications (MSpec)
Its been a while since I evaluated and evolved my approach to BDD. The way […]
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.