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 "Dag H. Wanvik (JIRA)" <ji...@apache.org> on 2009/07/01 02:14:47 UTC
[jira] Updated: (DERBY-3178) DataSourceTest uses
ConnectionEventListener but never verifies that events are getting fired
[ https://issues.apache.org/jira/browse/DERBY-3178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dag H. Wanvik updated DERBY-3178:
---------------------------------
Issue Type: Bug (was: Test)
> 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: Bug
> Components: Test
> Affects Versions: 10.4.1.3
> Reporter: Mamta A. Satoor
> Assignee: Mamta A. Satoor
> Fix For: 10.3.2.1, 10.4.1.3
>
> 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.