www.fooberry.com

I recently marked over 130 tests with [Ignore] in order to get our build to go return to green. It made me cringe to do it, but we lost our local database instance several months ago and many of the tests required it. That was a good 70% of them. The other 30% purely fell victim to apathy. When our local database instance was pulled, so was our build server, as well as other tools (a whole other post :S).

So since the build server stopped waving our failing tests in our face, about 40 test went on failing for months. Out of the entire test suite of 600, the 40 tests are only 7%, but hat 7% was mostly heavy financial calculation. An important 7% of our app.

This whole experience reminded me how lazy we are as a whole, but that’s OK. We have tooling (if we use it) to allow us to stay lazy. Maybe lazy has too negative of a connotation. How about focused. It reminds me of Don’t Make Me Think!. Except with developers, it’s “Don’t Make Me Do”. I don’t want to run my all my unit tests, analyze my code, increment my version numbers, or anything else not related to my business customer. If infrastructure is plumbing we abstract away from the application, so is the process. I want to increment my version number as much as I want to write a database logger.

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 for a way to run unit tests in all open documents, but haven’t found that one yet.