moq | Interface mocking tool for go generate | Mock library

Problem has been resolved thanks to @Dennis Doomen.

An issue about not executing method immediately was in the implementation of the spff.GetSymbols() method which uses yield return so it wasn't really related to unit testing.

I've got an answer from one of NUnit collaborator under this thread: https://github.com/nunit/nunit/issues/4090

Long story short - make sure that you are creating new DbContext instance each time when it's needed and just reuse the "options" to point out on which InMemory database should they operate:

Your issue is that you are running the Moq setup after the mocked object has been used. By then it's already too late. You just need to run the .Setup(...) commands at the start.

It's also worth noting that using a shared mock can be problematic if multiple tests need the setups to be different. Some tools can run tests in parallel which may screw things up, or in a different order which can cause things to be more brittle.

Code smell aside, I would suggest using an actual IServiceProvider to avoid having to arrange the behavior

Both HttpWebRequest constructors are obsolete and should not be used. You have to use the static function "Create" to create a new instance of the HttpWebRequest class:

HttpWebRequest myReq = (HttpWebRequest)WebRequest.Create("http://www.contoso.com/");

To solve your issue, use the HttpClient class instead. This class has a parameterless constructor.

How about this:

In line with the new Azure SDK guidelines public methods are marked virtual so they can be mocked:

A service client is the main entry point for developers in an Azure SDK library. Because a client type implements most of the “live” logic that communicates with an Azure service, it’s important to be able to create an instance of a client that behaves as expected without making any network calls.

1. Each of the Azure SDK clients follows mocking guidelines that allow their behavior to be overridden:
2. Each client offers at least one protected constructor to allow inheritance for testing. All public client members are virtual to allow overriding.

In case of the BlobClient mocking can be done like this*:

You can mock classes with Moq. You just need to create a new Mock with valid constructor parameters. In your case:

Your code isn't working because you are using the Returns overload that allows you to get hold of the parameters provided to the invocation, but you're not providing the type and you're not providing all of them. It's not about them having default values, it's that you're not providing the definition that Moq expects.

There's probably a few ways you can cut this. Given: