[
https://issues.apache.org/jira/browse/CASSANDRA-15579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17149093#comment-17149093
]
David Capwell commented on CASSANDRA-15579:
-------------------------------------------
One thing to say, Cassandra tests tend to lack failure mode testing, so would
be good to start looking into where things could fail and if we have tests to
handle them; thats what I was doing for repair.
We also have issues with upgrades, and issues with older SSTable formats.
Another thing to look into is the interaction between different features, if
enabling/disabling a feature interacts with something, make sure we include
testing with it (and failures there).
> 4.0 quality testing: Distributed Read/Write Path: Coordination, Replication,
> and Read Repair
> --------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-15579
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15579
> Project: Cassandra
> Issue Type: Task
> Components: Test/unit
> Reporter: Josh McKenzie
> Assignee: Andres de la Peña
> Priority: Normal
> Fix For: 4.0-beta
>
>
> Reference [doc from
> NGCC|https://docs.google.com/document/d/1uhUOp7wpE9ZXNDgxoCZHejHt5SO4Qw1dArZqqsJccyQ/edit#]
> for context.
> *Shepherd: Blake Eggleston*
> Testing in this area focuses on non-node-local aspects of the read-write
> path: coordination, replication, read repair, etc.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
