Using Moq Callback to set values to drive tests
How to set a value on an object passed to a mock to drive conditional logic further in the system under test
How to set a value on an object passed to a mock to drive conditional logic further in the system under test
Asserting numbers of items in a list or collection is vital to unit tests, but which to choose?
Harnessing the power of the C# 8 using declarations to aid with unit test assert clarity
Looking at how to verify calls to Ilogger based extension methods using Moq.
Are you asserting too much in your unit tests? Is this due to potential code smells? Let’s discuss.