Recently I was asked about backing in unit tests into an existing project. In particular I was asked A) was possible and B) is it worth it. In short my answers to both these are Yes and Yes. However, backing in unit tests is not without its challenges. I thought today I would go express my experiences...
In my last post I think I struck a cord with some people in my post 'Unit tests taking too much time'. My intent was NOT to sound like an elitist Agilist or any else of that nature. My intent was simply to put a post out there about the misperception (in my opinion) about how writing unit tests...
Up until a few months ago I had never even attempted to use mocks ( NMock , RhinoMock , etc). Every time I would read about Mocking I thought to myself, this is kinda cool, but seems to be a waste of energy. At the time I saw Mocks as only a way to create ‘placeholders’ for business/data classes. I did...
Just to pass this along. I was needing to raise events in NMock and I came across this post on how to Raise Events in NMock2 . This is a good post with clear examples. Enjoy
I am looking for feedback from the group. I am pretty new to using mocks for my unit tests and I am not sure what the standard approach in the community for usage of mocks in regards to how/where they are stored in your test application. After refactoring some of my tests to use mocks I quickly noticed...