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…]
I’ve worked in teams that do enums in 2 different ways. One is storing enums as lookup tables in the DB. The other is to keep it in code. I’m going to show how they are used and my preferred way. Disclaimer, this is just a personal preference. There are pros and cons in both … [Read more…]
Previously I showed how to mock SendAsync method in HttpClient so it can be unit tested. In this post, I will show how to mock the SendAsync method in DelegatingHandler so it can be unit tested as it allows you to mock the response and your test does not need to make a real Http request. The first problem … [Read more…]
Previously I showed how to log all HttpClient outgoing requests. I later added some logics for adding default headers in the SendAsync method in OutgoingHttpClient. I wanted to unit test this to make sure my logic is correct. I thought I could mock the HttpClient the normal way but since the SendAsync method in HttpClient is not virtual, I get … [Read more…]
In my previous post, I showed my implementation for logging outgoing HTTP requests. In this post, I’ll show my implementation for logging outgoing SOAP requests using custom endpoint behaviour. First I have an implemention of the IClientMessageInspector. IMessageLoggingInspector is mainly for DI. public interface IMessageLoggingInspector : IClientMessageInspector { } public class MessageLoggingInspector : IMessageLoggingInspector { // AfterReceiveReply is … [Read more…]
My current project has lots of outgoing requests to third parties including HTTP and SOAP requests. I was tasked to log all outgoing requests in their raw form. In this post, I’m going to show my implementation for logging outgoing HTTP requests. I’m using .Net Core 2.1 and HttpClientFactory for this solution. I could use … [Read more…]
I like using the Builder pattern for building test data in unit tests. Builder pattern makes it clean if I need to build a valid object, in the unit tests, with the minimum required properties. It also makes it clear when I need to build an object and explicitly specify a different value for any of … [Read more…]
I was tasked to build a method that would take in any object and a string that specifies the property to be returned. Let’s say we have a complex object as followed public class Company { public string Name { get; set; } public string ABN { get; set; } public int YearFounded { get; … [Read more…]
So often we have to use DateTime.UtcNow or DateTime.Now in our code. To make it easier to mock current date time in unit test and to make unit tests more resilient, it’s better to not use DateTime.UtcNow or DateTime.Now directly but rather pass it in or make it as a property. Let’s say we have a … [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…]