db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Closed: (DERBY-4817) Convert the client server compatibility tests to junit.
Date Thu, 03 Feb 2011 18:10:29 GMT

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

Knut Anders Hatlen closed DERBY-4817.

    Resolution: Duplicate

Closing as duplicate of DERBY-2316.

> 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:
>            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.
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message