title: How to deal with angular module's config function when unit testing?
body: <p>When setting up a unit test suite for an angular application using Karma/Jasmine, is it recommended to include the js with the app module's <code>config</code> function in the test's files?</p>
  
  <p>I've read that it is suggested to exclude this from testing, however that seems awkward because there's often critical setup that happens in the <code>config</code> function that would prevent the application from working.</p>
  
  <p>What's the best practice around this? Create a mock config function that does the same thing in a 'mocked' manner?</p>
  
  <p>I'm running across this issue myself but want to understand the broader strategy:
  <a href="https://stackoverflow.com/questions/18876290/how-do-unit-test-with-angular-translate">How do unit test with angular-translate</a></p>