Golang

313 readers

3 users here now

This is a community dedicated to the go programming language.

Useful Links:

Rules:

Posts must be relevant to Go
No NSFW content
No hate speech, bigotry, etc
Try to keep discussions on topic
No spam of tools/companies/advertisements
It’s OK to post your own stuff part of the time, but the primary use of the community should not be self-promotion.

founded 1 year ago

MODERATORS

[email protected]

Don't use mocks (joeblu.com)

submitted 1 year ago by [email protected] to c/[email protected]

9 comments fedilink hide all child comments

Always interesting to hear different points of view on this subject. Personally I think mocks make sense to capture complex sets of interactions or otherwise difficult to reach error conditions, so I don't think it's a do or do-not kind of thing.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 5 points 1 year ago

I'm a Java guy so not sure how different it is. It bothers me when people make such absolute statements like "don't use mocking" and then give examples like this,

What happens in dep1 gets a new function Add and you change your code to use it? You break your test, even though no behavior in your code has changed. We shouldn’t be rewriting tests that have the exact same inputs and expected outputs.

What the heck do they mean no behavior in my code changed? They just said in the previous sentence that I changed my code. There are some better arguments but that one is weak.