[
https://issues.apache.org/jira/browse/DERBY-6397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan updated DERBY-6397:
-----------------------------------
Attachment: derby-6397-1a-multiple_vms.diff
derby-6397-1a-multiple_vms.stat
Attaching patch 1a, which makes it possible to run the compatibility tests with
multiple JVMs (i.e. versions and/or vendors).
The patch has only been tested with various Oracle and OpenJDK VMs, and the
testing was conducted a while back. Should definitely get exposed to more
testing.
Some work should be done to make sure the effects of the various options/system
properties are sane/understandable, and maybe some people would prefer using a
property file instead of specifying all the system properties on the command
line.
Not sure if I'll be able to work on this any time soon, so I'm leaving the
issue unassigned.
To test, apply the patch, turn on tracing and/or debug to see the effect on the
test combinations (or use a graphical runner). Specify VMs with
-Dderby.tests.compat.jvm.1=/path/to/bin/java, you can specify up to 9 if you
have the urge to do that :) The running VM will always be included.
> Run the rewritten compatibility test with multiple JVMs
> -------------------------------------------------------
>
> Key: DERBY-6397
> URL: https://issues.apache.org/jira/browse/DERBY-6397
> Project: Derby
> Issue Type: Improvement
> Components: Test
> Affects Versions: 10.11.0.0
> Reporter: Kristian Waagan
> Attachments: derby-6397-1a-multiple_vms.diff,
> derby-6397-1a-multiple_vms.stat
>
>
> The compatibility test was rewritten to JUnit and is now living in
> java/testing/org/apache/derbyTesting/functionTests/tests/compatibility/ .
> While supporting most of the features of the old test, it has been unable to
> run the tests with combinations of multiple JVMs.
> This issue tracks the work required to add the functionality of running the
> compatibility tests with multiple Java VMs.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
