[
https://issues.apache.org/jira/browse/CASSANDRA-15538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17206170#comment-17206170
]
Alex Petrov commented on CASSANDRA-15538:
-----------------------------------------
bq. it's incredibly helpful reproducing things discovered in diff testing.
Diff testing is a great tool, and I think it's super useful, but Harry
hopefully goes much further than it does. First, we exercise all kinds of
queries in harry: we insert, update, and delete data, so it exercises code
paths that are not touched by diff.
> Is there also a "generative fuzz without specific workload context" role it
> serves? If so, is that something we can enumerate here? Thinking something
> like a gdoc to brain dump "here's the scenarios we can and should test with
> tool X to confirm subsystem Y" or something like that.
We've tried our best to make Harry functional enough to test pretty much
anything, but we don't have a single-button solution for anything just yet. In
other words, if you want to exerice "SRP after RR", you can still use Harry
machinery to create and validate data, but you'll have to create specific
message filters that create a situation yourself. In future, we'll create
failure scenarios and improving the way we simulate stuff, too. I'm always
happy to answer any questions about how to implement certain things using Harry.
> 4.0 quality testing: Local Read/Write Path: Other Areas
> -------------------------------------------------------
>
> Key: CASSANDRA-15538
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15538
> Project: Cassandra
> Issue Type: Task
> Components: Test/dtest/java, Test/dtest/python
> Reporter: Josh McKenzie
> Priority: Normal
> Fix For: 4.0-beta, 4.0-triage
>
>
> Reference [doc from
> NGCC|https://docs.google.com/document/d/1uhUOp7wpE9ZXNDgxoCZHejHt5SO4Qw1dArZqqsJccyQ/edit#]
> for context.
> *Shepherd: Aleksey Yeschenko*
> Testing in this area refers to the local read/write path (StorageProxy,
> ColumnFamilyStore, Memtable, SSTable reading/writing, etc). We are still
> finding numerous bugs and issues with the 3.0 storage engine rewrite
> (CASSANDRA-8099). For 4.0 we want to ensure that we thoroughly cover the
> local read/write path with techniques such as property-based testing, fuzzing
> ([example|http://cassandra.apache.org/blog/2018/10/17/finding_bugs_with_property_based_testing.html]),
> and a source audit.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
