dtchepak
commented
8 years ago I really like this idea, including being able to customise the autovalues used (say, all IEngine values should automatically get SimulatedEngine instances). I've never needed it enough to invest the time into getting it working though.
Is this something you've got time to look in to? I think the per-substitute option would be easiest to implement (I'm not sure how to handle the global config option, particularly if tests are running over multiple threads?).
mbordogna
stnoa
It would be nice to have auto values disabled. I ran into a scenario for casting that was failing with the auto value, it took a bit for us to figure out this was due to a chain that was automatically created due to missing mocks because of the auto value and proxy in a service locator pattern due to differences in registration and the more generalized super interface.
If null was returned from the unmocked method, it would have been more obvious. There has been a few other times where this has been the case but when using nSubsitute to fill in the gaps with DI container testing for service locator patterns utilized for complex factories, having auto values made the issue less obvious.
So I am proposing an option for disabling auto values, either at construction or as a global setting. Like a ForExpicitMocks method, so that when used it will know to return null for anyting not mocked and does not attempt to create proxies.