In Moq 4.13 they introduced the It.IsAnyType type which you can using to mock generic methods. E.g. public interface IFoo { bool M1<T>(); bool M2<T>(T arg); } var mock = new Mock<IFoo>(); // matches any type argument: mock.Setup(m => m.M1<It.IsAnyType>()).Returns(true); // matches only type arguments that are subtypes of / implement T: mock.Setup(m => m.M1<It.IsSubtype<T>>()).Returns(true); … Read more
I believe your only choice right now is to explicitly include the bool parameter in the setup for Foo. I don’t think it defeats the purpose of specifying a default value. The default value is a convenience for calling code, but I think that you should be explicit in your tests. Say you could leave … 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
Moq creates an implementation of the mocked type. If the type is an interface, it creates a class that implements the interface. If the type is a class, it creates an inherited class, and the members of that inherited class call the base class. But in order to do that it has to override the … Read more
Webforms is notoriously untestable for this exact reason – a lot of code can rely on static classes in the asp.net pipeline. In order to test this with Moq, you need to refactor your GetSecurityContextUserName() method to use dependency injection with an HttpContextBase object. HttpContextWrapper resides in System.Web.Abstractions, which ships with .Net 3.5. It is … Read more
It.IsAny only allows Moq to match future invocations of method calls if used within the Setup construct. When Setup is called Moq just adds the method call to its cache of already-set-up method calls. Note that the argument to Setup in your example has type Expression<Func<IFoo, bool>>. Since you are passing in an Expression, the … Read more
I recently created Moq.Sequences which provides the ability to check ordering in Moq. You may want to read my post that describes the following: Supports method invocations, property setters and getters. Allows you to specify the number of times a specific call should be expected. Provides loops which allow you to group calls into a … Read more
Moq and other similar mocking frameworks can only mock interfaces, abstract methods/properties (on abstract classes) or virtual methods/properties on concrete classes. This is because it generates a proxy that will implement the interface or create a derived class that overrides those overrideable methods in order to intercept calls.
ADDENDUM: As the other answer states, the purpose of .Verifiable is to enlist a Setup into a set of “deferred Verify(…) calls” which can then be triggered via mock.Verify(). The OP’s clarification makes it clear that this was the goal and the only problem was figuring out why it wasn’t working, but as @Liam prodded, … Read more
I managed to solve it by creating a FakeDbSet<T> class that implements IDbSet<T> public class FakeDbSet<T> : IDbSet<T> where T : class { ObservableCollection<T> _data; IQueryable _query; public FakeDbSet() { _data = new ObservableCollection<T>(); _query = _data.AsQueryable(); } public virtual T Find(params object[] keyValues) { throw new NotImplementedException(“Derive from FakeDbSet<T> and override Find”); } public … Read more