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.
Integration Test Brought to you by Powershell & NUnit – with a Little Specification Syntax for Flavoring
One of the tools I?ve used the last half of a year and really enjoyed […]
Code Cast 30 – Story Teller with Jeremy Miller
The venerable Jeremy Miller joined us to talk about YAIJMOSP (Yet Another Impressive Jeremy Miller […]
MOQ Mothers
Am I the only one who does this? I like to use Object Mothers in […]
MSpec – Take 2
About a year ago, I remember first hearing about Machine.Specifications (github) and trying it out […]
VS Live Las Vegas Session Materials
I promised several people in my sessions I would post materials I used on ElegantCode.com, […]