Thanks for looking at the patch, Dag. Committed revision 1431948.
I have no reason to believe there are other ordering bugs, so I don't think we need to change it to run with fixed execution order now. However, I added some code to the tearDown() method to print the names of all tables, procedures and function that live in the APP schema after each test case has completed, and found that testDuplicates() leaves a procedure called PROCDUP and testDynamicResultSets() leaves one called INSERTCAUSINGROLLBACK. If other test cases depend on the existence of those procedures, ordering may affect the result. I don't know if there are such dependencies, but I think we should make the two test cases clean up after themselves in any case. I'll post a follow-up patch.