<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Aug 13, 2014 at 6:54 PM, Marcin Tustin <span dir="ltr"><<a href="mailto:Marcin.Tustin@dealertrack.com" target="_blank">Marcin.Tustin@dealertrack.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="white" lang="EN-US" link="blue" vlink="purple">
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">It’s not question of terminology. What happens if I let the test call it’s super is impossible to anticipate (but in practice will be some kind of exception).
Even if it successfully calls the super methods, the output won’t be defined by this code, but some other code, so I can’t usefully test anything about it other than its type. If it doesn’t work, then I have to deal with those exceptions, but then I can’t
very well distinguish between exceptions originating in the code I’m testing, and exceptions in the super methods. It’s all the usual reasons for mocking out calls.</span></p></div></div>
<br></blockquote></div><div class="gmail_extra"><br></div>I think about my tests differently. I don't care how the feature is implemented all I care about is if it works. Mocking super means that you can't refactor your code without changing tests.</div>
<div class="gmail_extra"><br></div><div class="gmail_extra">Do you have any real code to share? I suspect that the method you had in your original post isn't real production code. But if I just look at that example the only thing I would mock is `do_some_stuff` because it's a collaborator.<br clear="all">
<div><br></div>-- <br>David<br>blog: <a href="http://www.traceback.org" target="_blank">http://www.traceback.org</a><br>twitter: <a href="http://twitter.com/dstanek" target="_blank">http://twitter.com/dstanek</a><div>www: <a href="http://dstanek.com" target="_blank">http://dstanek.com</a></div>
</div></div>