You can’t, at least not with Moq. But more importantly, you shouldn’t. First off, you don’t test methods, you test behaviours. Second, in order to test behaviours, you exercise a type’s public API and verify the outcomes of that exercise. Private methods are implementation details. You don’t want to verify how things get done, you … Read more
LicenseManagerService.Verify(m => m.LoadProductLicenses(),Times.Once); By calling the LicenseManagerService property, you’re creating a new mock object. Naturally, no invocations have ever been performed on this instance. You should change this property’s implementation to return the same instance every time it is called.
Another way in Moq to call protected member is the following template: In your class, with protected member mark your function as virtual. For example: public class ClassProtected { public string CallingFunction(Customer customer) { var firstName = ProtectedFunction(customer.FirstName); var lastName = ProtectedFunction(customer.LastName); return string.Format(“{0}, {1}”, lastName, firstName); } protected virtual string ProtectedFunction(string value) { return … Read more
Unit tests should not use the container at all. Dependency Injection (DI) comes in two phases: Use DI patterns to inject dependencies into consumers. You don’t need a container to do that. At the application’s Composition Root, use a DI Container (or Poor Man’s DI) to wire all components together. How not to use any … Read more
You can’t mock extension methods directly, so your best bet is to drill down until you hit the properties and methods upon which the extension method depends that are mockable. In this case, IIdentity.GetuUserId() is an extension method. I’d post it, but the library is not currently open source, so you’ll have to see for … Read more
I was able to solve it using ConfigurationBuilder. Hope this will help var appSettings = @”{“”AppSettings””:{ “”Key1″” : “”Value1″”, “”Key2″” : “”Value2″”, “”Key3″” : “”Value3″” }}”; var builder = new ConfigurationBuilder(); builder.AddJsonStream(new MemoryStream(Encoding.UTF8.GetBytes(appSettings))); var configuration= builder.Build();
MoqSecurityAdminHelper.Setup(x => x.GetAllQuestions(It.IsAny<Boolean>())) .Returns((bool param) => param ? someResult : someOtherResult );
You get a compiler error because you return a task that doesn’t match the type the async method returns. You should return Task<Member> instead of simply Task<object>: repository.Setup(r => r.GetMemberAsync(email)).Returns(Task.FromResult<Member>(null));
If the SaveItem() method is virtual or abstract, and you’re not setting Callbase = true, then the method should be re-implemented to do nothing by the mock. You should be able to do: mockDb.Setup(d => d.SaveItem(It.IsAny<object>())).Verifiable(); … test here … mockDb.Verify();
Moq cannot mock non virtual methods on classes. Either use other mocking frameworks such as Type mock Isolator which actually weaves IL into your assembly or place an interface on EmailService and mock that.