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.

4
  • Thanks! One question though: you say that with the tdd approach I could extract the private complexity to another public method. Now this is tested individually and it's call becomes so easy that it doesn't need to be tested anymore. Commented Jan 11 at 9:54
  • Isn't it the case that now, my original test has at least to make sure that the call was made? All complex test cases can of course be outsourced, but I should somehow validate that the call was made at all..how to do that? I don't like mocks here ... Commented Jan 11 at 9:56
  • What benefits do you expect to realize if you could write such a test? "Design is what we do to get more of what we want than we would get by just doing it." What's the "what we want" that motivates "validate that the call was made at all" ? Commented Jan 11 at 16:20
  • The call is important because it validates the complex input data. The validation function could be outsourced and tested individually, but tests of the public methods need to make this call to catch the plenty possible "unhappy" paths. I could make sure the call was made with just testing one invalid case of many to make sure the call was made but it feels not right somehow Commented Jan 11 at 16:46