title: MVP Pattern : Separating the database dependency from the presenter?
body: <p>Whenever I try to actually unit test a presenter and a mocked view, I end up running into too many database dependencies</p>
  
  <pre><code> public EditAccount(IAccountEditPage _view, ISession _session, IResponse _response)
   {
  
   }
  
   public void view_SaveUser()
   {
     //Class that takes the view's data and persists it to DB  
   }
  </code></pre>
  
  <p>Obviously I can't write unit tests for this presenter because I have a concretion of using my model class that has a strong database dependency.</p>
  
  <p>How am I supposed to removed the dependency on the database without constructor injecting every class that touches the database in my presenter?  I don't want to do this every time in every view I have.  </p>
  
  <p>I'm using moq, if it helps.</p>
  
  <p>Edit : Also I should mention that the code in "view_SaveUser" is very lean and isn't direct database access or anything like that.  It's usually only a few lines.  I'm not overstepping the scope of the presenter, AFAIK.</p>