[
https://issues.apache.org/jira/browse/CASSANDRA-8607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15244888#comment-15244888
]
Christopher Batey commented on CASSANDRA-8607:
----------------------------------------------
I have a fork of cassandra stress that has unit tests. I plan to submit it
soon. This could be this ticket or I could raise a separate one as I don't plan
to add e2e/dtests yet which I think would be very valuable.
> Introduce unit tests or dtests for cassandra-stress
> ---------------------------------------------------
>
> Key: CASSANDRA-8607
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8607
> Project: Cassandra
> Issue Type: Improvement
> Components: Tools
> Reporter: Benedict
> Assignee: Christopher Batey
>
> Right now we don't have any tests in place to ensure we don't break stress.
> In general we've relied on simply noticing problems as part of the
> development process, since we've typically developed features in tandem with
> related c* functionality, so we would see if we'd gotten it wrong. However
> now that it is being used more widely, we could do with some automated
> testing to ensure we haven't accidentally broken anything. If we mock up some
> non-random random classes and permit them to be swapped in wherever necessary
> we could construct some known dataset / visitation etc behaviours that elicit
> all of the edge cases.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
