Software Engineering Stack Exchange is a question and answer site for professionals, academics, and students working within the systems development life cycle. It only takes a minute to sign up.
Sign up to join this community
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?
If you don't care about the state the method returns in unit test, this is a code-smell. You need to reevaluate the design of this method as it is likely doing too many things at once.
The a method should generally return void if it alters the state of its owning object. This is not a hard rule, but if what it is returning is complicated enough to need to be mocked, then I'd guess your method is not one of the exceptions to the rule.
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