monkey VS go-timejumper

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!

Write a test. Then write the implementation. If you find it hard to test, because your test needs to know too much about the implementation, or impossible to test because of side effects, iterate by injecting dependencies. Time itself could be a dependency. I wrote https://github.com/ghostsquad/go-timejumper just for that purpose (as an example).

Example, if you have something that depends on time, inject this: https://github.com/ghostsquad/go-timejumper