title: Junit @BeforeClass and @AfterClass behavior in case of multiple test cases
body: <p>Folks,</p>
  
  <p>Say I have a complicated sub-classed test suite that I run regularly. As a part of this, I am trying to ensure that each test class is executed strictly one after the other, and that <code>Test2</code>'s <code>@BeforeClass</code> method will NOT start before <code>Test1</code>'s <code>@AfterClass</code> is done. Is this a valid assumption to make? </p>
  
  <p>An Example Scenario:</p>
  
  <p>Class <code>TestBase</code> has an <code>@BeforeClass</code> and an <code>@AfterClass</code> method.</p>
  
  <p>Class <code>T1</code> derives from <code>TestBase</code>.</p>
  
  <p>Class <code>T2</code> derives from `TestBase.</p>
  
  <p>We run <code>T1</code> and <code>T2</code> together from Ant / Eclipse. There are some common static objects from TestBase reused between <code>T1</code> and <code>T2</code>, meaning I have to be totally sure that these are destroyed completely in <code>AfterClass</code> before the next round of <code>BeforeClass</code> start to initialize the same. Can I be sure of this with the basic usage outlined above?</p>
  
  <p>I have a strong suspicion that this is not happening, but simplistic tests are not proving the same. Documentation doesn't talk about this either. So I want to ensure that I am not trying to solve a systemic issue that can be solved otherwise.</p>