[
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_v1.example_compatibilitytest.properties
derby-2316_v1.diff.txt
First version of
java/testing/org/apache/derbyTesting/functionTests/tests/junitTests/compatibility/CompatibilityCombinations.java
which is intended as a replacement for
java/testing/org/apache/derbyTesting/functionTests/tests/junitTests/compatibility/testScript.xml.
CompatibilityCombinations.java reads paths for Derby versions and Jvm versions
from the file 'compatibilitytest.properties' in '${user.dir}'.
An example of 'compatibilitytest.properties' is included in the patch.
Test results are reported as
Attempted 'embedded vs. network client' tests: 9, OK: 9, Failed: 0, Time: 54.0
seconds
Attempted 'server - network client' tests: 324, OK: 324, Failed: 0, Time:
1132.0 seconds
More detailed reports are found in '${user.dir}/system' in files following this
name pattern:
1. Embedded_compatDB_summary.log
which is a summary of
1.n Embedded_TrunkVMj15lib_vs_ClientVM-j15lib_clientTrunk report files
and
2. ServerClient_compatDB_summary.log
which is a summary of
2.m ServerVM-j16lib_server10.1.2.1_vs_ClientVM-j14lib_clientTrunk report files
I ran
'java -Djava.security.policy="<NONE>" junit.textui.TestRunner
org.apache.derbyTesting.functionTests.tests.junitTests.compatibility.CompatibilityCombinations'
using derby-2316_v1.example_compatibilitytest.properties as
compatibilitytest.properties
on Linux 2.6.17-1.2142_FC4.
Result:
Attempted 'embedded vs. network client' tests: 9, OK: 9, Failed: 0, Time: 54.0
seconds
Attempted 'server - network client' tests: 324, OK: 324, Failed: 0, Time:
1132.0 seconds
CompatibilityCombinations.java still contains lots of 'DEBUG' statements and
the javadoc could probably be expanded...
> 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
> 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.
