title: Many Test classes or one Test class with many methods?
body: <p>I have a PersonDao that I'm writing unit tests against.</p>
  
  <p>There are about 18-20 methods in PersonDao of the form - </p>
  
  <pre><code>    getAllPersons() 
      getAllPersonsByCategory()
      getAllPersonsUnder21() etc
  </code></pre>
  
  <p>My Approach to testing this was to create a PersonDaoTest with about 18 test methods testing each of the method in PersonDao</p>
  
  <p>Then I created a PersonDaoPaginationTest that tested these 18 methods by applying pagination parameters.</p>
  
  <p>Is this in anyway against the TDD best practices? I was told that this creates confusion and is against the best practices since this is non-standard. What was suggested is merging the two classes into PersonDaoTest instead.</p>
  
  <p>As I understand is, the more broken down into many classes your code is, the better, please comment.</p>