When you’re testing your code, you’re most likely doing different types of tests – e.g. you might be doing real unit testing, integration testing, etc. In Rebus, we had the need to do contract tests1, which is a test that
One of my former colleagues blogged about using AutoFixture as an auto-mocking container the other day, which got me thinking about auto-mocking with Windsor. Although I’ve never used auto-mocking myself, a few months ago, I answered a question on StackOverflow,
Today I came across Shouldly, as I followed a link in a tweet by Rob Conery. I have a thing for nifty mini-projects, so I immediately git clone http://github.com/shouldly/shouldly.git‘d it, and pulled it into a small thing I am building.
In the previous post I showed how easy it is to install an IoC container at the system boundary of your ASP.NET MVC application and have it resolve everything from there. But what I did not show, was where the
Usually, when writing code, you adhere to some conventions on how your stuff should work. At least I hope you do – otherwise your code is probably a mess! Sometimes, these conventions can be enforced by using some patterns to
[this post is outdated – too much has happened since the first CTP] This is the first post in a series of at least four about ASP.NET MVC, which I am planning. The series will show a way to build