I am not aware of any limitation of nsubstitute Few years ago I was an adept of moq, and now I have a preference for nsubstitute. I like the syntax (you call directly the method vs setup.), I think NSubstitute has the best syntax and is the most readable of all the frameworks (but this … Read more
Actually, the accepted answer mocks a synchronous exception being thrown, that is not the real async behavior. The correct way to mock is: var myService = Substitute.For<IMyService>(); myService.GetAllAsync() .Returns(Task.FromException<List<object>>(new Exception(“some error”))); Let’s say you had this code and GetAllAsync() try { var result = myService.GetAllAsync().Result; return result; } catch (AggregateException ex) { // whatever, do … Read more
In theory there is absolutely no problem mocking a concrete class; we are testing against a logical interface (rather than a keyword interface), and it does not matter whether that logical interface is provided by a class or interface. In practice .NET/C# makes this a bit problematic. As you mentioned a .NET mocking framework I’m … Read more
This happens because of NSubstitute syntax specific. For example in: ((IQueryable<Blog>) mockSet).Provider.Returns(data.Provider); NSubstitute calls the Provider’s getter, then it specifies the return value. This getter call isn’t intercepted by the substitute and you get an exception. It happens because of explicit implementation of IQueryable.Provider property in DbQuery class. You can explicitly create substitutes for multiple … Read more
You can use an actual Configuration instance with in-memory data. //Arrange var inMemorySettings = new Dictionary<string, string> { {“TopLevelKey”, “TopLevelValue”}, {“SectionName:SomeKey”, “SectionValue”}, //…populate as needed for the test }; IConfiguration configuration = new ConfigurationBuilder() .AddInMemoryCollection(inMemorySettings) .Build(); //… Now it is a matter of using the configuration as desired to exercise the test //… string value … Read more
I assume that your Commander object will take the arguments and puts them in an array which it then uses to call the Processor mock. Your foos variable is another array which you create on your setup. Arrays don’t compare equal to each other even if they have the same elements. So NSubstitute will complain … Read more