db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mamta A. Satoor (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3178) DataSourceTest uses ConnectionEventListener but never verifies that events are getting fired
Date Wed, 07 Nov 2007 03:24:50 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540660
] 

Mamta A. Satoor commented on DERBY-3178:
----------------------------------------

I forgot to mention that I didn't find any test case in DataSourceTest.java which will trigger
Connection error event. The existing test cases only test Connection closed event.

> DataSourceTest uses ConnectionEventListener but never verifies that events are getting
fired
> --------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3178
>                 URL: https://issues.apache.org/jira/browse/DERBY-3178
>             Project: Derby
>          Issue Type: Test
>          Components: Test
>    Affects Versions: 10.4.0.0
>            Reporter: Mamta A. Satoor
>            Assignee: Mamta A. Satoor
>             Fix For: 10.3.1.5, 10.4.0.0
>
>         Attachments: DERBY_3178_diff_ver1_Nov_06_2007.txt
>
>
> Derby has a junit test called DataSourceTest in jdbcapi package. This test registers
ConnectionEventListener for various Connection objects but never verifies that events from
those Connection objects are getting delivered to the listeners. Prior to this test's conversion
to junit, there were System.out.println in the test but since this test is not cannon based
anymore, those printlns have been commented out. I will soon submit a patch where this test
will have asserts to make sure that Connection events are getting fired.

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


Mime
View raw message