[CASSANDRA-16026] Nodetool unit test coverage

• Type: Improvement
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 4.0.1
• Component/s: Tool/nodetool
• Complexity: Normal
• Platform: All
• Assignee: Unassigned
• Reporter: Berenguer Blasi
• Created: 04/Aug/20 09:18
• Updated: 17/Feb/22 08:19
• Resolved: 03/Aug/21 19:41

Description

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.

Issue Links

• is caused by: CASSANDRA-15583 4.0 quality testing: Tooling, Bundled and First Party
• is duplicated by: CASSANDRA-16298 Nodetool unit testing
• relates to: CASSANDRA-16200 Nodetool ring unit testing
• relates to: CASSANDRA-16227 Nodetool Netstats and tablestats tests
• relates to: CASSANDRA-16230 Nodetool tpstats, gossipinfo, enable and disablebinary tests