I'm a believer in creating unit tests for systems, to a point. For example, most of my systems have a data access layer, and a model (aka "domain" or "business") layer, which often follows the Repository pattern. (I'm not sure I see the value of always separating the Repository from the model, but that's another blog post.)

Lately, my data access layers use ADO.NET Entity Frameworks. I feel that there is very little point to writing unit tests for EF libraries. However, I need to test my Repository layer, without complicating my data access layer by trying to force EF to cooperate with some dependency injection framework (typically Unity).

To this end, I've been pleased to discover and use NDbUnit. This package can be fetched using NuGet.

This is how NDbUnit works,...