[
https://issues.apache.org/jira/browse/DERBY-3088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12559792#action_12559792
]
Myrna van Lunteren commented on DERBY-3088:
-------------------------------------------
Revision 612684 improves the ServerPropertiesTest a little in that it now runs
with either classes or jars - there is one fixture that needs jars, so there's
an if in place.
Also uses a new BaseTestCase method assertExecJavaCmdAsExpected instead of a
similar one just in this test, and modified the test
NetworkServerControlClientCommandTest to use it instead of the Utilities method.
The execJavaCmd method in Utilites would hang on the pr.waitFor() method if
there was more than a little data in the buffer, so it didn't work for all
cases I needed to know a java command executed. I left it in place, for now.
> convert to junit, or otherwise eliminate version in tests which require an
> update of the master in the release management process
> ---------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-3088
> URL: https://issues.apache.org/jira/browse/DERBY-3088
> Project: Derby
> Issue Type: Improvement
> Components: Build tools, Test
> Reporter: Myrna van Lunteren
> Assignee: Myrna van Lunteren
> Attachments: DERBY-3088_ServerPropertiesTest.diff,
> DERBY-3088_ServerPropertiesTest2.diff
>
>
> There are a number of tests that require a master update every time the
> version number is bumped.
> This is a tedious and error prone detail in the release management process.
> Currently affected masters are listed in tools/release/build.xml:
> java/testing/org/apache/derbyTesting/functionTests/master/DerbyNetClient/metadata.out
> java/testing/org/apache/derbyTesting/functionTests/master/DerbyNetClient/odbc_metadata.out
> java/testing/org/apache/derbyTesting/functionTests/master/metadata.out
> java/testing/org/apache/derbyTesting/functionTests/master/odbc_metadata.out
> java/testing/org/apache/derbyTesting/functionTests/master/NSinSameJVM.out
> java/testing/org/apache/derbyTesting/functionTests/master/checkToursDB.out
> java/testing/org/apache/derbyTesting/functionTests/master/testclientij.out
> java/testing/org/apache/derbyTesting/functionTests/master/testProperties.out
> It would streamline the release process if these tests in particular were
> either converted to junit, or if the version numbers would be eliminated.
> Note: there already is a bug for metadata.java conversion: DERBY-2242
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
