title: Is it right to mock look up tables in a unit test?
body: <p>when you write a test for the logic layer, you mock the data access layer that's used, because you don't want the test cases to be dependent on each other.</p>
  
  <p>But what about lookup tables ?
  lets say you have a logic that calculcates value depending on size in <strong>Sizes</strong> table:</p>
  
  <p>Small   1<br>
  Medium  2<br>
  Large   3</p>
  
  <p>Now, do you mock this table somehow in your test? using a dictionary for ex.? when the table changes (<em>a real config table will contain hundreds of values, and sometimes will not be in simple key-value form</em>) how do you keep code and table insync?</p>
  
  <p>or you bend this rule... and get values directly from database?
  but what if tomorrow i change the data source? or i cannot access the database somehow? aren't test cases supposed to run in whatever conditions ?</p>
  
  <p>what's the best approach?</p>