Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

7
  • 3
    Every introductory piece I've read about mocking seems to hit this problem. Once you start mocking things the tests always seem to be more complicated than the code they're testing. Obviously this is less likely to be the case when testing real-world code, but its quite disheartening when you're trying to learn. Commented Oct 13, 2010 at 3:52
  • @Carson63000 If it's a simple test testing something with a tested mock, the complexity is split and under control (, I think). Commented Nov 12, 2010 at 10:43
  • 21
    But then how do you test the test tests? Commented Feb 20, 2011 at 21:30
  • +1. Item 1 could be a requirements error. Can only be prevented by reviewing the requirements. Probably out of the programmer's hands unless they are also the requirements analyst Commented Feb 27, 2012 at 17:30
  • 2
    @ocodo: The same way you watch the Watchers. :) Commented Mar 13, 2017 at 13:33