Refactor old tests TC30 and TC31

Udai, I don't think there's any value in overloading the suite() method in this test case. JUnit 3.x has a default convention where any method will be added to the suite if it has a prefix of 'test'. As we have followed that convention throughout, please drop this method.

A few more observations:

a) Using code statements in setUp() like this

LOG.info("Test30 Started");

could be slightly mis-leading, as the methods setUp() and tearDown() will be executed before and after each test case (as opposed to once per test class).

b) the populateDatabase*() methods should imho not be included in the test suite (if we decide to keep a suite method, which in my opinion is completely redundant).

c) Shouldn't the populateDatabase*() methods be included in the setUp() method, so that each test has a clean database before it is being executed ?

I hope to be able to review your patch in detail taking Werner's comments into account later on today. ATM I only recognized that some changes are contained twice in the patch. In addition you seam to have also moved entities not used by TC30 but other TC3x tests.

Thanks for your comments ....I have modified accordingly ....I hope this time it will be fine.

Yes, much better. But there was no need to actually remove the populateDatabase*() methods and move the code into the setUp() method. Just leave those methods as is, and simply call them from the setUp() method.

done!!

Great. Please leave the call to

_db = getJDOManager(DBNAME).getDatabase();

in the setUp()method, though (as that's where it belongs to ...) .. .

Updated patch with a bunch of small improvements to test30. According to the tests i extracted 2 tests of test30 into a seperate test class but most was about code formating. Having said that I had not enough time to test them.

Udai, could you please test my changes and review test31 yourself with respect to the changes I made to test30.

Thanks Ralf , I will take care of all this next time when I will code.....There was some minor problems in the patch of tests you provided in context of running them....I fixed those ...now its perfect....I will modify the TC31 accordingly

Again removed test30_call table from ddl script and also had to do some code formatting at test31. Of what I recall there where class variables that where only needed by one method and did not conform to our naming conventions for class variables and a lot of lines with wrong indention. Also one of the table names did not start with test31. In addition some of the tables got not reset before test execution.

I have fixed all this myself and added release notes so that the patch now is ready to commit.

Having said that all tests already run without failures against mysql.