Doh! Speaking of Resharper, some marketing guy from M$ called me a few days ago and asked how I liked Visual Studio 2008. I told him that it the stock/ out-of-the-box refactorings in VS suck and that they should either include Resharper functionality in VS (for free) or they should copy Eclipse’s refactorings. OMG, VS 2008 doesn’t even let you refactor the basics like method return types and parameter names.

I’m totally with you on this one, Sarah. I usually practice Test First Development. I like to go one step further and give the parameters a name, to further clarify my intentions. For example:

public void SuccessulUpdateOfCarDeatilsShouldReturnSuccessResponse()
{
CarController controller = new CarController();

int dummyCarId = 42;
string carRegistration = “car registration”;
string colour = “colour”;
string engineIdentificationNumber = “engineIdentificationNumber”;

controller.UpdateCarDetails(dummyCarId, carRegistration, colour, engineIdentificationNumber);

Assert.AreEqual(HttpStatusCode.OK, controller.Response);
}

Giving the parameters a name is especially beneficial when the method under test has many overloads. Note that I also changed the expected value 200 to HttpStatusCode.OK.

Keep up the good work.

An alternative to rolling your own simulator for http services is the http-impersonator project. it can record http responses and then replay them.

http://code.google.com/p/http-impersonator/

Or you mean it is better to move the validation into another place? Which call anti-corruption layers ??

Thanks