[
https://issues.apache.org/jira/browse/CASSANDRA-9161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15175991#comment-15175991
]
Benjamin Lerer commented on CASSANDRA-9161:
-------------------------------------------
{quote}Just to clarify, we're talking about unit tests here.{quote}
I know. I was just mentioning them because of the problems we faced with
upgrade tests due to the randomness of how the data is distributed.
{quote}To be clear, that ticket wasn't trying to suggest we randomize
absolutely everything.{quote}
I know that a lot of thing cannot be randomize. I am absolutly not in favor of
random testing. For flushing, the main problem that I have seen is that only
the read or write path for memtables was tested not the one for SSTables. This
problem is for me a problem of test coverage (we are not testing properly some
part of the code). Personnaly, I would prefer to have a tool able to detect
that type of issues than having some random flushes. Now, it is possible that
you have other problems in mind which my be more difficult to discover.
> Add random interleaving for flush/compaction when running CQL unit tests
> ------------------------------------------------------------------------
>
> Key: CASSANDRA-9161
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9161
> Project: Cassandra
> Issue Type: Test
> Reporter: Sylvain Lebresne
> Labels: retrospective_generated
>
> Most CQL tests don't bother flushing, which means that they overwhelmingly
> test the memtable path and not the sstables one. A simple way to improve on
> that would be to make {{CQLTester}} issue flushes and compactions randomly
> between statements.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
