title: Testing multiple public methods that call the same private method
body: <p>I'm trying to figure out whether it's an API design flaw, it is actually OK, or the SRP is being violated.</p>
  
  <p>I have 2 public methods <code>initialize()</code> and <code>onListRefresh()</code>. Both of them call the same private method <code>updateList()</code>. The only difference between both of them is that <code>initialize()</code> also check for a null argument to throw an exception.</p>
  
  <p>The issue is that in order to test both public methods, I practically have to copy and paste the same mocks, stub, expectations and assertions, which are all for what happens on the private method, and it feels wrong. So which one is it:</p>
  
  <ol>
  <li>Is there a flaw in the public API design?</li>
  <li>It's all right, that's how it's supposed to be.</li>
  <li>SRP is being violated by using <code>initialize()</code> to do both checking for an argument AND calling <code>updateList()</code></li>
  </ol>