News for hackers. Stuff that matters.
Re:Why I don't mock by pling on Wednesday May 28, 2014 @10:24AM (#7810058)
Assume that when you have N consumers of an interface then your coupling is N. Mocks consume an interface as does your codebase so your coupling is at least N=2 whereas your codebase alone was N=1. By using mocks, programmers cause coupling to increase so programmers should stop using mocks to decrease coupling.
Re:Why I don't mock by the_af on Wednesday May 28, 2014 @07:11PM (#7813576)
This is technically true but I don't think it's a good argument against mocking or test doubles.

By this reasoning, the test suite itself causes coupling to increase. For any component C, you have at least N=2: when it's used in production code, and when it's tested. If you don't test C, you reduce N to 1. This doesn't sound like a good argument against testing, though.

Re:Why I don't mock by SideburnsOfDoom on Wednesday May 28, 2014 @11:36AM (#7810786)
> Mocks consume an interface as does your codebase so your coupling is at least N=2 whereas your codebase alone was N=1.

I really hope that you're not being serious here.

Re:Why I don't mock by pling on Wednesday May 28, 2014 @12:53PM (#7811346)
100%. Its called efferent coupling.
Re:Why I don't mock by SideburnsOfDoom on Wednesday May 28, 2014 @01:11PM (#7811490)
It's answer which is technically 100% right; and practically 100% missing the point. So it seemed facetious.