With dependency injection, we get the benefit that we can never "forget" to inject a (mock) dependency. Does TypeMock provide a way to get a similar asssurance?
For example, if a service is modified to use some new dependency, say a FileSystem object, and we forget to have tests mock it out, the test may still function, but it will become slow, and it can have undesirable side-effects such as creating files and folders. This is unlikely to be detected, whilst highly undesirable, particularly in the long run. It seems essential to prevent this scenario.
