[
https://issues.apache.org/jira/browse/DERBY-4817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12981188#action_12981188
]
Knut Anders Hatlen commented on DERBY-4817:
-------------------------------------------
The compatibility tests can be run as JUnit tests (converted in DERBY-2316).
See instructions here:
http://svn.apache.org/viewvc/db/derby/code/trunk/java/testing/org/apache/derbyTesting/functionTests/tests/junitTests/compatibility/README.html?revision=1051493&view=co#Running%20the%20Tests%20from%20JUnit
Should we close this issue as a duplicate?
> Convert the client server compatibility tests to junit.
> -------------------------------------------------------
>
> Key: DERBY-4817
> URL: https://issues.apache.org/jira/browse/DERBY-4817
> Project: Derby
> Issue Type: Improvement
> Components: Test
> Affects Versions: 10.6.1.0
> Reporter: Mamta A. Satoor
>
> The client server compatibility test resides in
> org.apache.derbyTesting.functionTests.tests.junitTests.compatibility package.
> There is a script named testScript.xml which does the task for trying all
> different combinations of listed jvms, server versions and client versions
> and then it invokes (I think) a junit suite CompatibilitySuite to do more
> client server testing. The problem is that while trying different
> combinations in the script, we start/ping/stop network server and any errors
> from these steps do not get caught anywhere. One example of a bug that didn't
> get detected as compatibility test failure is DERBY-3644. Only a manual
> inspection of the script output will show any problems. It will be nice if we
> can convert this to junit and thus making it unnecessary to do a manual
> lookup of the script output.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
