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] Updated: (DERBY-2316) Convert compatibility/testScript.xml to JUnit
Date Thu, 07 Jun 2007 16:44:25 GMT

     [ https://issues.apache.org/jira/browse/DERBY-2316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Ole Solberg updated DERBY-2316:

    Attachment: derby-2316_v2.diff.txt

The attached patch(derby-2316_v2.diff.txt) changes '..../tests/junitTests/compatibility/CompatibilityCombinations.java'
to allow other testsuites than jdbcSuite (org.apache.derbyTesting.functionTests.tests.junitTests.compatibility.CompatibilitySuite)
to be used in testing Derby client version vs. Derby server version compatibility.

The testsuite to be used is now specified in the file 'compatibilitytest.properties'.

I need this functionality specifically in testing BlobClob client version vs. server version
compatibility using '..../tests/jdbcapi/BlobClob4BlobTest.java' in the CompatibilityCombinations

I have also taken care of Rick's suggestion for further improvements 1).

The patch has been tested running
java -Xmx256m -Djava.security.policy="<NONE>" junit.textui.TestRunner org.apache.derbyTesting.functionTests.tests.junitTests.compatibility.CompatibilityCombinations

I will submit the neccessary modifications to run '..../tests/jdbcapi/BlobClob4BlobTest.java'
in the CompatibilityCombinations framework in a separate JIRA.

> 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:
>         Environment: All
>            Reporter: Ole Solberg
>            Assignee: Ole Solberg
>            Priority: Minor
>         Attachments: derby-2316_v1.diff.txt, derby-2316_v1.example_compatibilitytest.properties,
> 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.

View raw message