db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ole Solberg (JIRA)" <j...@apache.org>
Subject [jira] Created: (DERBY-2316) Convert compatibility/testScript.xml to JUnit
Date Fri, 09 Feb 2007 15:17:05 GMT
Convert compatibility/testScript.xml to JUnit
---------------------------------------------

                 Key: DERBY-2316
                 URL: https://issues.apache.org/jira/browse/DERBY-2316
             Project: Derby
          Issue Type: Improvement
          Components: Test
    Affects Versions: 10.3.0.0
         Environment: All
            Reporter: Ole Solberg
         Assigned To: Ole Solberg
            Priority: Minor


I have started converting compatibility/testScript.xml to JUnit to
1) be able to more dynamically specify which combinations to test, 
2) get standard JUnit reports from the test, and
3) more easily include the compatibility test in the regression test runs.


I plan to use a property file (patterened after the current ant.property file for 
the compatibility test), to specify jvm and derby library locations.


With the growing number of jvm and derby versions I also think that it should be 
possible to specify a number of different kinds of compatibility test combinations,
for example:

a) the current way, which is all combinations of derby and jvm on both 
   server and client.                                            [(derbys*jvms)*(derbys*jvms)]
b) Current trunk client and jvms  vs.  all server derbys and jvms. [(1*jvms)*(derbys*jvms)]
c) All clients and jvms  vs.  current trunk server and jvms.        [(derbys*jvms)*(1*jvms)]
d) Exact specification of the combinations to be tested.         [(N*M)*(X*Y)]

Which kind of test to run should be specified in the property file.



-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message