title: How to organize jUnit tests to separately cover packages and entire program?
body: <p>This question is about your experience and industry best practices. 
  Please comment on what i did and see whether it makes sence. Let me know how you handle the same problem</p>
  
  <p>When i write my tests, i usually focus on on package at a time. Each class in src gets its own test class. Life is good. For a given package, i come up with a single class that is responsible for running all tests in a package. For example (<code>A.java</code>) that looks like this:</p>
  
  <pre><code>@RunWith(Suite.class)
  @Suite.SuiteClasses( { One.class, Two.class, Three.class })
  public class _A {
  
  }
  </code></pre>
  
  <p><strong>Concern 1: This introduces 1 extra class that is used to run all tests for that package.</strong> </p>
  
  <p><strong>Concern 2: My tendency is to precede that class with an underscore (to make sure it shows up on top. Understore (i was told), is a bad taste ..</strong></p>
  
  <p><strong>Question: Is it common to create a separate test class to test a given package?</strong></p>
  
  <p>Pattern as shown above repeats for every package i have. For each package i have under /test, i have an _Package{x}Tests.java</p>
  
  <p>Additionally, at the root directory under /test, i have a mother of all tests class which includes all package tests</p>
  
  <pre><code>/test
      _ApplicationTests.class
  
  @RunWith(Suite.class)
  @Suite.SuiteClasses( { _A.class, _B.class, _C.class })
  public class _ApplicationTests {
  
  }
  </code></pre>
  
  <p><strong>Concern 1: I really would rather avoid default package, but at the same time, i like very much to see "first test that shows up" to be the master test file</strong></p>
  
  <p><strong>Concern 2: Again (i must have read this somewhere .. ) MasterTests class starts with an underscore (for consistency i gues</strong>)</p>
  
  <p>How do you guys handle this? Is what i described an acceptable approach? </p>
  
  <p>For me (personally), i am very attracked to the idea of having an option to run "all tests" and "all package tests" separately.</p>
  
  <p>Thanks, and please let me know.</p>