AutoFixture VS Refit

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.

A lot of people have given you good replies, but have you looked at Refit?

Another question that rises is, would it be better to use some HttpClient package to handle the requests, like Refit in combination with Polly. But then again, it seems Refit also uses the HttpClient factory, which was a bad thing according to the previous?

Define a Refit client interface with the following for each API endpoint, e.g. GET /foo:

Use RestEase to create your own client library. Refit is a very similar and more popular library. IMO RestEase is an improvement over Refit and I prefer it, but either will solve your problems. Both are libs that have you build interfaces describing the API endpoints, then the library handles all the boilerplate code that calls HttpClient.

Refit - simple, typed REST clients: https://github.com/reactiveui/refit

I'd advise using this https://github.com/reactiveui/refit tool for HTTP requests. It saves a lot of time for serialization, deserialization and exception handling.

Use Refit, and let manage the live of HttpClient. Also, Refit will give you a strongly typed client around an API. All you have to write is the interface. Ain't that neat ? If you can't, use the HttpClientFactory to create the HttpClient instance: https://learn.microsoft.com/en-us/dotnet/architecture/microservices/implement-resilient-applications/use-httpclientfactory-to-implement-resilient-http-requests

Use RestEase to create your own client library. Refit is a very similar and more popular library. IMO RestEase is an improvement over Refit and I prefer it, but either will solve your problems. Both are libs that have you build interfaces describing the API endpoints, then the library handles all the boilerplate code that calls HttpClient.

The controller is simple and use the Refit library to abstract the PokéAPI call and then, returns the data.

To be fair, Refit is pretty great.