[
https://issues.apache.org/jira/browse/DERBY-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myrna van Lunteren updated DERBY-2031:
--------------------------------------
Derby Info: (was: [Patch Available])
switching off patch available, as Bryan said, it may not be proper to change
the visibility. In the mean time, this test is running as a junit test vai the
JavaHarnessTest. Not exactly a conversion, but a step in the direction.
> 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.0.0
> Reporter: Knut Anders Hatlen
> Assigned To: Julius Stroffek
> Priority: Minor
> Attachments: d2031.diff, d2031.stat
>
>
> 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.
