It could just be that the module of code under test doesn't do enough. If you need to mock a service, database, other service, error-handler, etc ... but the c

It could just be that the module of code under test doesn't do enough. If you need to mock a service, database, other service, error-handler, etc ... but the core logic is just verifying that <some condition> is met, then this is going to be the case. Personally I like to avoid mocking for cases like this, since integration tests can usually suffice. As you said, though, it could also be the framework. If you're in C#-land, Moq is pretty terse with the syntax so the actual mocking code isn't that big.