You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Ke Han (Jira)" <ji...@apache.org> on 2022/12/26 03:46:00 UTC
[jira] [Commented] (CASSANDRA-18128) Fuzz testing Cassandra's upgrade process
[ https://issues.apache.org/jira/browse/CASSANDRA-18128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17651917#comment-17651917 ]
Ke Han commented on CASSANDRA-18128:
------------------------------------
[~aratnofsky] Hi Abe, I opened a ticket here to explain our testing mechanism. I'll fill in the details gradually since our tool is still under active development. :)
Have a lovely Christmas!
> Fuzz testing Cassandra's upgrade process
> ----------------------------------------
>
> Key: CASSANDRA-18128
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18128
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Ke Han
> Priority: Normal
>
> We developed a tool to fuzz testing Cassandra's upgrade process. Our target is to improve the reliability of both full-stop upgrade and rolling upgrade.
> This ticket is to explain our testing mechanism. We will describe it from a high level and gradually fill it in details. (The tool is still under active development)
> Our tool is composed of bug triggering and failure detection.
> * Bug Triggering
> ** Input Generation
> ** Configuration Generation
> ** Fault Injection
> * Failure detection
> ** Node crash
> ** Error log message
> ** Semantic error
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org