Dapper VS AutoFixture

In both samples to get all records and to get a single record works fine but there is a better way to perform the same work using NuGet package Dapper. Dapper is extremely easy to use and built with performance in mind. In the source code provided the basic operations are covered, to take things to the next level and read the information at GitHub, the following page and other code samples in the following repository.

In this article learn how to use Dapper an open-source object-relational mapping (ORM) library for .NET and .NET Core applications. Unlike many articles out there, this one will provide source code to try everything out that is shown in an easy-to-follow way by beginning with a single table then in part two of this series will work with multiple tables.

Dapper

I will be using Dapper - a simple object mapper for .Net along with MySqlConnector.

Maybe the more basic approach to dapper is their documentation https://github.com/DapperLib/Dapper the readme but again most likely you not gonna understand

I think EF Core & EF are the successors to LINQ to SQL that you'd wanna look into, and/or Dapper if you wanna go lower.

The main maintainers of Dapper no longer work at Stack, but they're active enough to comment on recent pull requests: https://github.com/DapperLib/Dapper/pull/1887.

MarieDB and dapper https://github.com/DapperLib/Dapper

Yes, it does feel like some of the "standard stuff" in other more nuanced languages are missing (especially miss AutoFixture ngl). Some of those are a conscious decison by the golang team for example.

Our first test is very easy, I like to name my tests as MethodName_GivenCondition_ShouldExpectedResult to follow the pattern, I have added GetById_GivenRecordDoesNotExist_ShouldReturnNull and I am going to leavarage excellent AutoFixture to get a new Guid as parameter. For this test we don't need arrange part, we would skip to the act and then assert. For Assertion I am going to use FluentAssertions. For this test we need to assert the returned result is null.

The next test to talk about, is that if this was a bank, we would have multiple customers, who can hold multiple accounts that we need to calculate the interest for. You could manually construct these objects if you want, but I'm going to use a package called AutoFixture to make life easier.

AutoFixture is an amazing library that simplifies the process of creating test data in .NET. If for some reason you don't use this fantastic tool, it's time to consider it. Today, I'm going to share some tips for using AutoFixture that will be beneficial for developers of all skill levels. Let's get started!

AutoFixture

Ensuring that your test is still readable and not bloated by the setup of those variables may be quite a challenge but hopefully no more with AutoFixture, let's see how!

One neat library for creating and generating test data is AutoFixture.  The creators describe it as follows:

First time I heard of Bogus, looks interesting, been using AutoFixture for those will definitely take a look at it.