Feed
Discussion
Mocking Imported Libraries in Golang Unit Tests
In my last post, I covered mocking using interfaces. In this one, I'll take that a step further and show how we can ensure that we're able to mock every imported lib in our tested functions by using private variables. tl;dr: you can check out a repo ...
Responses
Markdown supported · ⌘↵ to post
ALFRED OKORONKWO
This is quite good. Clearly defines what it means to write maintainable code. I'd love to see how it would have handled FileInfo.IsDir() although it could be taken care of with fstest.