[
https://issues.apache.org/jira/browse/CASSANDRA-9160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14562789#comment-14562789
]
Stefania commented on CASSANDRA-9160:
-------------------------------------
The patch is currently based on trunk but I would be inclined to have it in
2.2, especially if the rearrangements are substantial.
As for 2.1, provided the functionality of CQLTester is there, it should be
possible to have the CQL unit tests there as well. During the conversion from
Python to Java I encountered a number of times cases where the behavior was
specific to 2.2/3.0 or older versions and I only converted the latest behavior.
However, if we just run the tests against 2.1 it shouldn't take long at all to
just fix those few cases were the tests are failing due to an older version.
> 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)
