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…]
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…]
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…]
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
|
1 2 3 4 5 6 7 |
public class Article { [DatabaseGenerated(DatabaseGeneratedOption.Identity)] public int ArticleNumber { get; set; } public Guid Id { get; set; } public string Name { get; set; } } |
The DbContext looks like below
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 |
public class ArticleDbContext : DbContext { public DbSet<Article> Articles { get; set; } // More DbSet goes here public ArticleDbContext(DbContextOptions<ArticleDbContext> options) : base(options) {} protected override void OnModelCreating(ModelBuilder modelBuilder) { // Model creating logic goes here } } |
I have a ArticleRepository as … [Read more…]
It’s very common that we assert if two objects are equivalent in unit tests. Using FluentAssertion, this looks like the following
|
1 |
actual.ShouldBeEquivalentTo(expected); |
However, there are times where you want to exclude certain properties when comparing objects. This might be because the value of the property cannot be predicted or you just don’t want to include … [Read more…]
This post is part of a series of blog posts about bad codes or bad practices I’ve come across. Note that this is my personal opinion and some of the things I mention could be debatable. Post 1: Code review, why it matters Post 2: Not including JS, CSS and static content files in project Post … [Read more…]
I have a submit model with a property of type decimal that represents a percentage. I use the range attribute to only allow values from 0 to 100. I have a unit test where I use the Validator to test this validation on the submit model. However, when I pass in an input that’s outside the … [Read more…]
When unit testing a service, I tend to have a base class where I do all the setting up/initialisation. For each method in the service, I’d have a separate unit test class which derives from the base class. For example, if I want to unit test two methods GetAllNews and GetNewsById in SampleNewsService, I’ll have a SampleNewsServiceTestsBase … [Read more…]