What is the best way to Mock a return type if we don't care about the actual state of the object.
For example, I am Mocking a method whose return type is: IEnumerable<Document>
Now, I can add relevant Nuget package and add necessary namespace so the type Document is defined, however I actually don't need to test anything on the returned object and I feel it's an overkill to include the Nuget and add namespace.
What other alternatives are available instead of including the reference?
Document
, it means the code under test is usingDocument
, which means you already need the nuget/reference because you're referencing something that depends on it. No? – Telastyn Nov 28 '18 at 21:10