[
https://issues.apache.org/jira/browse/CASSANDRA-9210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14512515#comment-14512515
]
Benedict commented on CASSANDRA-9210:
-------------------------------------
There are lots places to take this kind of approach, and this is just a very
rough sketch. For instance, in reality, this test could be completely
automatically generated in its entirety, and the row verification could be
computed for us by the test. The insertion order could also be varied to be
certain it doesn't get screwed up in anyway, and we could permute all
interleavings of flushing with the inserts. We could automatically insert
unrelated deletes, or inserts with deletes. etc. etc.
> CQL Tests Should Operate Over All Types (etc)
> ---------------------------------------------
>
> Key: CASSANDRA-9210
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9210
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Benedict
>
> With some refactoring our CQL tests could cover all possible types for a
> given operation, and potentially different positions in the clustering
> component of a primary key, as well as differing adjacent items of data in
> the table being queried.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
