[jira] Issue Comment Edited: (DERBY-2031) Convert derbynet/testProtocol.java to JUnit

["Kathey Marsden (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/DERBY-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12617778#action_12617778 ] 

kmarsden edited comment on DERBY-2031 at 7/29/08 6:04 AM:
----------------------------------------------------------------

There was a problem with the new StressMultiTest removing the database directory because of  DERBY-3789.  Erlend was able to workaround that problem by making sure all the result sets were closed.  In this case it was not the database directory I think, but rather the test include file connect.inc. There must be a problem with the protocol test that it leaves a file handle open to the include file.


      was (Author: kmarsden):
    There weas a problem with the new StressMultiTest removing the database directory because of  DERBY-3789.  Erlend was able to workaround that problem by making sure all the result sets were closed.  In this case it was not the database directory I think, but rather the test include file connect.inc. There must be a problem with the protocol test that it leaves a filie handle open to the include file.

  
> 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.