Yeah, that seems like an overkill to me. The balance I do like to strike is to use interfaces for any classes that interact with the outside world, and then ha

Yeah, that seems like an overkill to me. The balance I do like to strike is to use interfaces for any classes that interact with the outside world, and then have those faked out. That way, I can use them to provide data to smaller units, or record that business logic recorded the data I expected. Obviously this doesn't fix if the DB interactions themselves are correct, but it's a start.