title: Android Junit Testing vs. Normal Junit Testing
body: <p>I'm taking over an android project and I wish to introduce unit tests to the project, to help avoid possible regressions.</p>
  
  <p>For normal java projects, I have two source folders: <code>src</code> and <code>test</code>. The <code>src</code> source folder contains all of my source files and my <code>test</code> source folder contains all of my unit tests, which I believe is pretty standard for keeping test separate from the source, so you don't have to ship with them.</p>
  
  <p>I've been doing some reading online and the approach with android apps looks to be a little bit different. Several examples talk about setting up a 2nd project for an <code>android test project</code> and then referencing the <code>android project</code>. </p>
  
  <p>I wish to confirm a few things:</p>
  
  <ol>
  <li>Is having a 2nd project for the testing the appropriate thing to do when it comes to testing android projects or am I just finding bad examples?</li>
  <li>Should all unit tests be android unit tests? E.g. Yes they should all be, or no I should mix between android unit tests and junit because junits have less overhead.</li>
  <li>What additional benefits do android unit tests give over junit tests? E.g. Handles to the emulator, etc.</li>
  </ol>