WireMock.Net VS Refit

I'd say that without wanting to refactor the code a little bit (maybe moving those HttpClients into a service so that they are easily mocked) your best bet would be to use something like WireMock or MockHttp.

WireMock

WiremockNet https://github.com/WireMock-Net/WireMock.Net

In this post, I'll explain how to create mocks for HTTP APIs in narrow integration tests using the WireMock.Net library.

Recently was pointed to WireMock for testing purposes.

I use WireMock (@ Java) to start a local webserver alongside the tests, this webserver will provide ‘real’ responses to the client. Here’s the C# equivalent: https://github.com/WireMock-Net/WireMock.Net

You could try out WireMock.Net: https://github.com/WireMock-Net/WireMock.Net/wiki/Using-WireMock-in-UnitTests

Use WireMock to mock responses from the endpoint that FooClient interacts with. This lets you exercise all of the code contained in FooClient in a realistic way, without using mocks, but still get the different responses you expect.

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.