[
https://issues.apache.org/jira/browse/DERBY-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12617776#action_12617776
]
Kristian Waagan commented on DERBY-2031:
----------------------------------------
Currently it is only possible to easily run the tests from classes.
Technically it is possible to run from jars in at least three ways, all with
some disadvantages:
a) Use unsealed jars.
b) Include the tests in the production jars.
c) Run with the jars in the boot classpath.
Note that these approaches can be used "temporarily", i.e. only to run the
tests and not for the distribution jars.
Regarding the failure, I haven't tested on Windows. Wasn't there a similar
problem with another test reported not so long ago?
> Convert derbynet/testProtocol.java to JUnit
> -------------------------------------------
>
> Key: DERBY-2031
> URL: https://issues.apache.org/jira/browse/DERBY-2031
> Project: Derby
> Issue Type: Improvement
> Components: Network Server, Test
> Affects Versions: 10.3.1.4
> Reporter: Knut Anders Hatlen
> Assignee: Kristian Waagan
> Priority: Minor
> Fix For: 10.5.0.0
>
> Attachments: d2031.diff, d2031.stat, derby-2031-1a-grammar_enum.diff,
> derby-2031-1a-grammar_enum.stat, derby-2031-2a-test.diff,
> derby-2031-3a-enable_test.diff, derby-2031-3a-enable_test.stat,
> derby-2031-3b-enable_test.diff
>
>
> testProtocol.java executes DRDA commands from a file written in a
> special-purpose language. The statements are very much like assertions, so it
> should be fairly easy to convert the test to JUnit.
> Suggested approach: Change the interpreter (TestProto.java) so that is uses
> Assert.fail() instead of System.err.println() and System.exit(), and
> BaseTestCase.println() instead of System.out.println(). It should also use
> TestConfiguration to get the host name and port number.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
