Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Wed, 3 Jun 2015 19:19:38 +0000 (UTC)
From: "Philip Thompson (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12819988.1428657301000.3368.1433359178353@Atlassian.JIRA>
In-Reply-To: <JIRA.12819988.1428657301000@Atlassian.JIRA>
References: <JIRA.12819988.1428657301000@Atlassian.JIRA>
 <JIRA.12819988.1428657301189@arcas>
Subject: [jira] [Commented] (CASSANDRA-9160) Migrate CQL dtests to unit
 tests
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Philip Thompson commented on CASSANDRA-9160:
--------------------------------------------

>From a TE perspective, I see no reason (other than the extra work) to not add this to 2.1 and 2.2, and I can see a lot of benefits. If you want, we can move backporting this into separate tickets?

> Migrate CQL dtests to unit tests
> --------------------------------
>
>                 Key: CASSANDRA-9160
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9160
>             Project: Cassandra
>          Issue Type: Test
>            Reporter: Sylvain Lebresne
>            Assignee: Stefania
>
> We have CQL tests in 2 places: dtests and unit tests. The unit tests are actually somewhat better in the sense that they have the ability to test both prepared and unprepared statements at the flip of a switch. It's also better to have all those tests in the same place so we can improve the test framework in only one place (CASSANDRA-7959, CASSANDRA-9159, etc...). So we should move the CQL dtests to the unit tests (which will be a good occasion to organize them better).


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