[
https://issues.apache.org/jira/browse/CASSANDRA-15502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17163378#comment-17163378
]
Berenguer Blasi commented on CASSANDRA-15502:
---------------------------------------------
[~dcapwell] 100% agree with you. If you read the last messages in
CASSANDRA-15583 this is what Sam and I are also coming to think. 15583 so far
solves _being able_ to test tooling easily. But as you say coverage in most
cases is minimal. I am going to go around tooling and report on coverage (50K
foot view) to see what's the best way forward and any LHF. Adding 100% coverage
to all tooling would be a mammoth multi-month thing imo, so we need to think
how best to navigate that when we get to that bridge :-)
> In Tree Tooling with Java 11
> ----------------------------
>
> Key: CASSANDRA-15502
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15502
> Project: Cassandra
> Issue Type: Task
> Components: Test/dtest, Test/fuzz, Tool/bulk load, Tool/cqlsh,
> Tool/diff, Tool/fql, Tool/nodetool, Tool/sstable, Tool/stress
> Reporter: David Capwell
> Assignee: David Capwell
> Priority: Normal
> Fix For: 4.0-beta
>
>
> This is to cover testing the various tools running on java 11.
> The scope of this testing is manual testing and not automated, different
> JIRAs should cover automation testing these tool.
> The tools in question are: nodetool, sstableloader, sstablescrub,
> sstableupgrade, sstableutil, sstableverify, fqltool, stress, auditlogviewer,
> compaction-stress, sstabledump, sstableexpiredblockers, sstablemetadata,
> sstableofflinerelevel, sstablesplit, and sstablerepairedset (many of these
> may be tested already in dtest)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
