[
https://issues.apache.org/jira/browse/CASSANDRA-8607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15245078#comment-15245078
]
Joel Knighton commented on CASSANDRA-8607:
------------------------------------------
I'm very interested in making sure your unit tests make it in and think this
ticket is an appropriate venue for such. Holding off putting myself as reviewer
for now in case someone more familiar with stress internals is equally/more
motivated to do so, but I'm willing to take it if no one else has the time.
> 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)
