[
https://issues.apache.org/jira/browse/DERBY-3385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12576314#action_12576314
]
Daniel John Debrunner commented on DERBY-3385:
----------------------------------------------
As a style issue I think the sysinfo code would be better as a test generic
utility in o.a.dt.junit.something since it is independent of MBeans or JMX.
As a community we do seem to have a habit of adding generic utilities into
specific tests which leads to the same utility in multiple places (but
sometimes implemented differently :-) Something the old test harness was very
prone to, it would be good if we can avoid this with Junit tests.
> 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.
