You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Benjamin Lerer (Jira)" <ji...@apache.org> on 2021/07/26 11:45:00 UTC

[jira] [Commented] (CASSANDRA-16026) Nodetool unit test coverage

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

Benjamin Lerer commented on CASSANDRA-16026:
--------------------------------------------

[~bereng] the scop of this ticket is pretty broad and lack some clarity on what need to be done. I will change the complexity level to avoid confusing newcomers.

> Nodetool unit test coverage
> ---------------------------
>
>                 Key: CASSANDRA-16026
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-16026
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Tool/nodetool
>            Reporter: Berenguer Blasi
>            Priority: Normal
>             Fix For: 4.0.x
>
>
> Nowadays the majority of nodetool testing happens outside the main java unit testing effort. A lot is done as separate dtests under python, some commands don't have dedicated tests, some only get tested as a side effect of some other test, etc.
> The purpose of this ticket is to improve unit test coverage as much as possible now that CASSANDRA-15583 allows us to perform java unit tests for the tool.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org