cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tyler Hobbs (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-9105) JMX APIs appear untested
Date Thu, 02 Apr 2015 20:18:54 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-9105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14393304#comment-14393304
] 

Tyler Hobbs commented on CASSANDRA-9105:
----------------------------------------

I recently added a JMX utility module to the dtests that should make this easier to cover:
https://github.com/riptano/cassandra-dtest/blob/master/jmxutils.py

> JMX APIs appear untested
> ------------------------
>
>                 Key: CASSANDRA-9105
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9105
>             Project: Cassandra
>          Issue Type: Test
>            Reporter: Ariel Weisberg
>
> Anything supported via JMX is part of the public API of the database.
> Node tool uses JMX but doesn't seem to have its own unit test and the dtest nodetool_test.py
is pretty sparse.
> For values returned by JMX for the purposes of reporting we should test as best we can
that we are getting "real" values end to end. Occasionally metrics end up with no values,
or values in the wrong units.
> For commands going the other direction they should be exercised. There is probably a
lot of coverage of commands since they may be used when testing the features those commands
are a part of so no need for duplication there.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message