It is, with a catch! You have to make sure method B is virtual and can be overriden. Then, set the mock to call the base methods whenever a setup is not provided. Then you setup B, but don’t setup A. Because A was not setup, the actual implementation will be called. var myClassMock = … Read more
Try the generic version of Returns: var matchSetupRepository = new Mock<IMatchSetupRepository>(); matchSetupRepository .Setup(ms => ms.GetAll()) .Returns<IEnumerable<MatchSetup>>(null); or: var matchSetupRepository = new Mock<IMatchSetupRepository>(); matchSetupRepository .Setup(ms => ms.GetAll()) .Returns((IEnumerable<MatchSetup>)null); Instead. Because you’re passing the function null (and there are two overloads of Returns), the compiler does not know which overload you mean unless you cast the argument … Read more
You can use .SetupGet on your mock object. eg. [Test] public void DoOneStep () { var mock = new Mock<PairOfDice>(); mock.SetupGet(x => x.Value).Returns(1); PairOfDice d = mock.Object; Assert.AreEqual(1, d.Value); } See here for further details.
You can probably use partial mocking in this scenario, although all your methods would need to be virtual: var mock = new Moq.Mock<RenewalService>(); mock.Setup(m => m.GetNextRenewalDate(It.IsAny<Guid>())).Returns(null); mock.CallBase = true; var results = mock.Object.IsLastRenewalOfYear(…);
Looking at the source code of the AsNoTracking() extension method: public static IQueryable AsNoTracking(this IQueryable source) { var asDbQuery = source as DbQuery; return asDbQuery != null ? asDbQuery.AsNoTracking() : CommonAsNoTracking(source); } Since source (your DbSet<Product> you’re trying to mock) is indeed a DbQuery (because DbSet is deriving from DbQuery), it tries to invoke the … Read more
For what it’s worth: instead of mocking an ILoggerFactory, you could also pass an instance of NullLoggerFactory. This NullLoggerFactory will return instances of NullLogger. According to the docs, this is a: Minimalistic logger that does nothing.
You can get rid of the call to Setup and Verifiable on your mock. Just use Verify. I created a little test-project, and this worked for me: using System; using System.Collections.Generic; using System.Linq; using Moq; namespace csharp { public class SomeDTO { } public class SomeRepository { public virtual void Write(List<SomeDTO> list) { } } … Read more
Try the following Assert.IsFalse(Enum.IsDefined(typeof(EnumType), Int32.MaxValue); Create((EnumType)Int32.MaxValue); It’s true that any value you pick for the “default” case could one day become a valid value. So simply add a test to guarantee it doesn’t in the same place you check the default.
The moq 4.13 introduced this feature. Now it is possible to verify if add\remove has been invoked. Therefore four new methods have been introduced: SetupAdd SetupRemove VerifyAdd VerifyRemove Example var mock = new Mock<IAdder<EventArgs>>(); mock.SetupAdd(m => m.Added += (sender, args) => { }); mock.Object.Added += (sender, args) => { }; mock.Object.Added += (sender, args) => … Read more
There are two ReturnsAsync extension methods in Moq ReturnsExtensions class.They have following parameters: (this IReturns<TMock, Task<TResult>> mock, TResult value) (this IReturns<TMock, Task<TResult>> mock, Func<TResult> valueFunction) As you can see one accepts value which should be returned by task, and another accepts delegate which will return value. When you are passing null compiler don’t know whether … Read more