You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-dev@db.apache.org by "Kathey Marsden (JIRA)" <ji...@apache.org> on 2009/05/07 19:21:30 UTC

[jira] Assigned: (DERBY-1402) Make checkerror command in protocol.tests that is used in derbynet/testProtocol.java to be able to fail gracefully

     [ https://issues.apache.org/jira/browse/DERBY-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kathey Marsden reassigned DERBY-1402:
-------------------------------------

    Assignee:     (was: Sunitha Kambhampati)

Unassigning due to inactivity.


> Make checkerror command in protocol.tests that is used in derbynet/testProtocol.java to be able to fail gracefully
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-1402
>                 URL: https://issues.apache.org/jira/browse/DERBY-1402
>             Project: Derby
>          Issue Type: Test
>          Components: Test
>    Affects Versions: 10.2.1.6
>            Reporter: Sunitha Kambhampati
>            Priority: Trivial
>
> checkerror that is used to check error cases and conditions in protocol.tests does not fail gracefully if it does not receive the expected codepoint.  This can cause problems as I noticed when working on DERBY-959.   Make changes so that the checkerror case in case of failures will fail and then proceed to the next testcase.
> This is a trivial fix, but I am opening a separate jira for this and not fixing this as part of DERBY-959 since I would want this fix to be backported to 10.1 at some point.. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.