Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Fri, 20 Mar 2015 14:55:38 +0000 (UTC)
From: "Ariel Weisberg (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12783401.1426803043000.157128.1426863338338@Atlassian.JIRA>
In-Reply-To: <JIRA.12783401.1426803043000@Atlassian.JIRA>
References: <JIRA.12783401.1426803043000@Atlassian.JIRA>
 <JIRA.12783401.1426803043943@arcas>
Subject: [jira] [Commented] (CASSANDRA-9011) Identify missing test coverage
 by component
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CASSANDRA-9011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14371409#comment-14371409 ] 

Ariel Weisberg commented on CASSANDRA-9011:
-------------------------------------------

I should add, this is also a catch all for "I saw bug XYZ in the wild and it would have been caught if we had this specific kind of coverage."

A lot of the really good tests come from regression tests for bugs that have shipped.

> Identify missing test coverage by component
> -------------------------------------------
>
>                 Key: CASSANDRA-9011
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9011
>             Project: Cassandra
>          Issue Type: Task
>            Reporter: Ariel Weisberg
>            Assignee: Benedict
>
> Identify components that have bad/missing coverage (could be whitebox or blackbox).
> Make suggestions for what kind of test would provide the necessary coverage for each component.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)