monkey VS httpmock

Code that's hard to test is just bad code. And unlike most dynamic languages you can't just override some internals in Go (though there are some arcane hacks you can pull of but only at full moon https://github.com/bouk/monkey).

This person did not read the license of the original library https://github.com/bouk/monkey/blob/master/LICENSE.md

I am a new gopher. I was looking into the Monkey Patching module and it is archived now. I was wondering if there is an alternative for that.

Here is an example of this in Go - but as he says, don't actually do this. https://github.com/bouk/monkey

I discovered this lib a few days ago. https://github.com/bouk/monkey it allows you to monkey patch entire functions, replacing them by whatever you want. Perfect for mocking. It's simple to use. The program is hard patching the code using assembly to replace the function address at runtime. You should not use this lib out of your tests since it's absolutely not safe. It's only compatible with linux and windows. But it works great!

We will use httpmock for this purpose. Inside function setupSuite(), where we created useCase and provided nil as a billingClient now we will pass mocked http client:

Alternatively, you could use an http mock library like https://github.com/jarcoal/httpmock, and override the urls the RealClient calls with a mock response in your tests.

To mock an API: https://github.com/jarcoal/httpmock to use when your code calls external APIs so you don't want your tests call the real API. No need to create an interface as you do.