This post I will show how to create a testing context which can be used in unit tests to automatically construct the testing target. My solution is based on this article from https://dotnetcoretutorials.com. I’ve customised it a bit to allow mock Target and automatically inject all the mocks during setup. The customisation will give you a mock … [Read more…]
It’s very common to use AutoMapper to map one object to another. However if not configured, unit testing functions that use AutoMapper will throw a missing mapping exception. I’ve seen in previous projects 2 different approaches developers use AutoMapper. I’m going to show how to configure AutoMapper in unit test for each of the approaches. … [Read more…]
In my new project, we use EF Core for ORM. We have unit tests for the repository layer where the DbContext is used. I’m going to show how to use in-memory database to create the DbContext. I’ll use the model below for example public class Article { [DatabaseGenerated(DatabaseGeneratedOption.Identity)] public int ArticleNumber { get; set; } … [Read more…]
I tend to name my unit tests with the following convention: NameOfMethod_Inputs_Should_ExpectedResult For example, I have a method called Multiply which multiplies two integer parameters. If I have a test case to test this method with 2 integers 3 and 4, the test would be called Multiply_3_And_4_Should_Be_12 This has been working well for me until I recently come … [Read more…]
When unit testing for null or white space string variable, I often find myself writing the same unit test 3 times but with different input for the string parameter. public class Sample { public static void RequiredStringParameter(string stringParam) { if (string.IsNullOrWhiteSpace(stringParam)) { throw new ArgumentException($”{nameof(stringParam)} is required.”); } // Logics go here } } [TestFixture] … [Read more…]