AutoFixture VS Flurl.Http

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.

Flurl and others

Is Flurl.HTTP the same as https://flurl.dev/ I assume? (It doesn't mention a specific http package)

As far as your code goes, take a look at flurl (https://flurl.dev/). It is oh so much cleaner and more readable than the httpclient stuff.

I would also add flurl to that list https://flurl.dev/. It's an amazing library and can be super helpful for quick one off API calls.

Linqpad for me, it's my go to scratch pad when testing out either new tech or edge cases and POCs than firing up a new console project. Especially when wanting to try out new nuget packages and see how they work. Even for messing with external apis I use it with Flurl, especially for apis that don't have any proper documentation.

If you working with api use flurl You can also read source code on github.

Flurl: