[ http://issues.apache.org/jira/browse/DERBY-2031?page=comments#action_12459049 ] Bryan Pendleton commented on DERBY-2031: ----------------------------------------
It seems undesirable to have to change the visibility of the actual code. I remember that we've had some similar discussions on the mailing list recently. For example, http://www.nabble.com/Re%3A-JUnit-unit-tests---parallel-test-three--p5711307.html Unfortunately, I can't remember what we decided was the best technique for situations such as yours. > Convert derbynet/testProtocol.java to JUnit > ------------------------------------------- > > Key: DERBY-2031 > URL: http://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. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
