Unit Testing
In reference to my previous post about collectively running unit tests, I thought I would offer this ReSharper tip. ReSharper’s unit test runner is just plain awesome. Why MSTests don’t work like that by default astounds me…and is enough reason for me not to use them (although there are several more). One option you have for aggregating which tests you want to run in a single session is to right click on the folder that contains their source, right click and either Run or Debug them. I’m looking...
I’ve been spending the better part of two days doing this same process over and over. It doesn’t feel like I’m testing anything of value. I am not doing it in the C# 3.0ish way, but it is better to explain it that way. I have a class and a façade (MyFacade) that I want to extend and test. class Foo { public string Name { get; set; }}class MyFacade { public IMyDependency Depend { get; set; }}interface IMyDependency { IList<Foo> GetAllFoos();} So I write my test first like a good boy person should....
Recently I’ve been able to extend my unit test code coverage as I’ve been introducing more features into our code base. I know this is something that should always be done, but for whatever reason, that’s not the case. What I’ve come to notice is our current method of organizing our unit test makes adding new features and test for new features awkward. Currently our unit tests align perfectly with the class they test. So for example, if we have a class: namespace MyCompany.Domain{ public class Foo{}...