anonymous wrote : Not sure if that was the point you were trying to make. | | But if so, then yes we need to set objects to null in teardown. I didn't check / know about the order on Constructors... but yes.. the point I was trying to make is JUnit will hold one instance of the class per test method. So we must make sure we set fields to null on the test. We could maybe make some simple and generic code on UnitTestCase::tearDown, using reflection. But we would need to make sure we all called super.tearDown at the end of our tearDown methods. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4249239#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...