[
https://issues.apache.org/jira/browse/DERBY-3385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12576250#action_12576250
]
Daniel John Debrunner commented on DERBY-3385:
----------------------------------------------
I'll commit the jdbc patch but it needs a follow-on change. This code is not
testing what it is meant to be testing:
DatabaseMetaData dbmd = getConnection().getMetaData();
int expected = dbmd.getDriverMinorVersion();
assertIntAttribute(expected, getJdbcMBeanObjectName(), "MinorVersion");
Since the suite wrapped the tests in a network server decorator, the
connection, DatabaseMetaData and hence the driver version are all coming
from the client's driver, whereas the JDBCMBean is wrapping the embedded
driver. While the versions are typically the same there is no requirement,
especially if folks try out combination testing.
> Tests for JMX Management and Monitoring
> ---------------------------------------
>
> Key: DERBY-3385
> URL: https://issues.apache.org/jira/browse/DERBY-3385
> Project: Derby
> Issue Type: Sub-task
> Components: JMX, Test
> Reporter: John H. Embretsen
> Assignee: John H. Embretsen
> Attachments: d3385_ant-junit-all.diff, d3385_jdbcMBeanTest_01.diff,
> d3385_versionMBeanTest_01.diff, d3385_versionMBeanTest_02.diff, TestJMXp9.java
>
>
> DERBY-1387 implements a new feature set in Derby: Java Management eXtentions
> (JMX), i.e. standards-based management and monitoring capabilities.
> As these are completely new features providing additional interfaces to a
> running Derby system, a set of functional regression tests should be added.
> The new tests should verify that Derby's public JMX API works as intended,
> and should be able to detect regressions in this area in the future. There is
> a functional specification (jmxFuncspec.html) attached to DERBY-1387 which
> may be used as reference.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
