title: JUnit 4 why should I not place my static import of Assert class in superclass
body: <p>I am moving an application from JUnit 3.x to JUnit 4.x.  Of course, my hundreds of test classes now need to statically import org.junit.Assert methods, or directly reference org.junit.Assert for each assertion.</p>
  
  <p>Most of these test classes extend a custom test case wrapper class (let's call it <code>CompanyTestCase</code>) so it is feasible for me to do this</p>
  
  <pre><code>public void assertEquals(final Object expected, final Object actual)
  {
      org.junit.Assert.assertEquals(expected, actual);
  }
  </code></pre>
  
  <p>but that seems somewhat clumsy, and smells bad to me in general.  However the little devil on my shoulder argues that this is one reason people create custom test superclasses in the first place.</p>
  
  <p>Help me understand the best way to tackle this problem -- I really don't want to believe that <a href="https://stackoverflow.com/questions/264680/best-way-to-automagically-migrate-tests-from-junit-3-to-junit-4">this post</a> is the answer, mostly because I want to believe that Java is mature enough not to require boilerplate changes of this type (DRY, etc.).</p>
  
  <p>As @blalasaadri points out, it would be nice to extend <code>org.junit.Assert</code>, but, being a Spring/Mule application, the test case wrapper already extends <code>org.springframework.test.context.junit4.AbstractJUnit4SpringContextTests</code>.</p>