I normally do not blog bile by reposting another sites news, but this news is rather importnat in regards to TDD with Isolator. I use Rhino Mocks 80% of the time for mocking, but that last 20% is Isolator. Why 20% – this is the real tough stuff to test. SharePoint, Silverlight, Tightly Coupled Legacy…
Continue Reading »
Communicating changes back to a source developer during a remote code review (when the review is done while the developer is not near) can be very difficult. Emailing the thoughts/changes/errors is an option, but this option has “no teeth”. These items are likely to get missed and most likely will not get addressed. My preferred…
Continue Reading »
Our main build broke today. We have about 53 projects in our solution (yes, its huge) and all of a sudden … pow … NAnt started timing out. Upon further investigation I noticed that the build was timing out at the following instance: Coverage Log: Coverage.Log Waiting for profiled application to connect…Connected Configuring Profiler……
Continue Reading »
While writing some code I needed to be able to access the the App_Data directory in my ASPNET MVC app. Doing this usually involves a Server.MapPath, but this wont work for my unit test. Here’s how you can get around it: var appDataPath = (string)AppDomain.CurrentDomain.GetData("DataDirectory") ?? AppDomain.CurrentDomain.SetupInformation.ApplicationBase; Now I have my data directory…
Continue Reading »
I’m a firm believer in the phrase: “What gets measured gets managed.” When it comes to unit testing code coverage is something we can use to measure how much of our code is under test. By no means does this mean that the code that is under test is actually covered by valid tests that…
Continue Reading »