Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Sun, 17 Apr 2016 20:23:25 +0000 (UTC)
From: "Christopher Batey (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12767131.1421158977000.250782.1460924605497@Atlassian.JIRA>
In-Reply-To: <JIRA.12767131.1421158977000@Atlassian.JIRA>
References: <JIRA.12767131.1421158977000@Atlassian.JIRA>
 <JIRA.12767131.1421158977456@arcas>
Subject: [jira] [Assigned] (CASSANDRA-8607) Introduce unit tests or dtests
 for cassandra-stress
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CASSANDRA-8607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christopher Batey reassigned CASSANDRA-8607:
--------------------------------------------

    Assignee: Christopher Batey

> 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)