Common default return value of functions with generics

I am writing unit tests for little tasks that are talking to the database. My test cases also include scenarios where a given object is not found in the database, and therefore I’d like to emulate that the queries return null.

Now, I managed to achieve this by using the following calls:

var _session = // database session
A.CallTo(_session).WithReturnType<Foo>().Returns(null);
A.CallTo(_session).WithReturnType<Bar>().Returns(null);
// ~10 more of these with just different types defined

however I was wondering if there is a way of setting this up as the default behaviour - so that all calls to _session with a generic parameter will return null by default?

I don’t know if it is possible in the first place, but it would probably be a nice feature.

[thomaslevesque]

What shall we do about the analyzer? I don’t think we need a separate issue, we can just say that this feature complete with docs, analyzer warning, etc.

Yes, I’ll reopen and submit a PR with the analyzer changes.

[blairconrad]

To expand, the way I thought @thomaslevesque’s suggestion would work would be

A.CallTo(fake).Where(…).WithNonVoidReturnType().Returns(null);

(or swap Where and WithNonVoidReturnType, as desired, like we can now with Where and WithReturnType<>)