title: Does JUnit set randomly properties to null?
body: <p>I have a series of tests methods which exactly depend on each other. I keep having problems with object being set to default state or just their properties being changed to null. In normal program, nothing like this ever happens. Setting things randomly to final seems to help, but I can't modify production code just because of tests.</p>
  
  <p>The fact that setting properties to final also means that it's not in my code - if my code was changing these, compiler wouldn't compile it (no reflection in my code).</p>
  
  <p>Before I dig even deeper in it, could you please tell me whether JUnit should be doing something like this? If yes, what rules can I read about it?</p>