Moq has an ability to run some code after the method is executed. It is called “Callback”. Modify your code this way and it will work: private IDataReader MockIDataReader() { var moq = new Mock<IDataReader>(); bool readToggle = true; moq.Setup(x => x.Read()) // Returns value of local variable ‘readToggle’ (note that // you must use … Read more
You need to call the generic overload of Callback with the specific types expected by the method. The following should work: sender.Setup(x => x.SendCommand(It.IsAny<MyCommand>(), false)) .Callback<ICommand, bool>((command, idFromContent) => { var myCommand = command as MyCommand; Assert.That(myCommand, Is.Not.Null); Assert.That(myCommand.Id, Is.EqualTo(cmd.Id)); Assert.That(myCommand.Name, Is.EqualTo(cmd.Name)); }) .Verifiable(); If the assertions fail in the callback then the test fails … 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.
try: logger.Verify(x => x.WriteData(Moq.It.Is<string>(str => str.StartsWith(“ABC”))), Times.Exactly(3)); you can see another example of It.Is: // matching Func<int>, lazy evaluated mock.Setup(foo => foo.Add(It.Is<int>(i => i % 2 == 0))).Returns(true); that comes from Moq documentation: https://github.com/Moq/moq4/wiki/Quickstart
You can use Verify. Examples: Verify that Add was never called with an UserMetaData with FirstName!= “FirstName1″: storageManager.Verify(e => e.Add(It.Is<UserMetaData>(d => d.FirstName!=”FirstName1”)), Times.Never()); Verify that Add was called at least once with an UserMetaData with FirstName== “FirstName1″: storageManager.Verify(e => e.Add(It.Is<UserMetaData>(d => d.FirstName==”FirstName1”)), Times.AtLeastOnce()); Verify that Add was called exactly once with FirstName == “Firstname1” and … 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
According to source code for MemoryCacheExtensions.cs, The Get<TItem> extension method makes use of the following public static object Get(this IMemoryCache cache, object key) { cache.TryGetValue(key, out object value); return value; } public static TItem Get<TItem>(this IMemoryCache cache, object key) { return (TItem)(cache.Get(key) ?? default(TItem)); } public static bool TryGetValue<TItem>(this IMemoryCache cache, object key, out TItem … Read more
If you need test cases for the Number or Message properties of the exception, you could use a builder (which uses reflection) like this: using System; using System.Data.SqlClient; // .NetCore using Microsoft.Data.SqlClient; using System.Linq; using System.Reflection; public class SqlExceptionBuilder { private int errorNumber; private string errorMessage; public SqlException Build() { SqlError error = this.CreateError(); SqlErrorCollection … Read more
I believe Lunivore’s answer was correct at the time it was written. In newer versions of Moq (I think since version 4.1 from 2013) it is possible to do what you want with the exact syntax you propose. That is: mock.Setup(m => m.VirtualMethod()).CallBase(); This sets up the loose mock to call the base implementation of … Read more
I see you are using EF core DbContext in your MovieRepository. So instead of using mock, Using EF Core InMemory database will be a great option for you. This will also reduce the complexity. Write your GetAllTest() method as follows: [Fact] public void GetAllTest() { var options = new DbContextOptionsBuilder<MovieDbContext>() .UseInMemoryDatabase(databaseName: “MovieListDatabase”) .Options; // Insert … Read more