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

Eric Evans commented on CASSANDRA-3300:
---------------------------------------

bq. Using cassandra-maven-plugin to start a cassandra server for running the 
integration tests.

The idea is that at some point, there will be an established set of tests that 
each driver must implement.  An automated system will then run each driver's 
test suite against the current, and some number of older versions of Cassandra. 
 All of this will be used as a sort of acceptance criteria for 
blessing/certifying/whatever.

Currently, having the tests connect to an already running Cassandra instance 
seems like the best way to make that work consistently against an arbitrary 
number of drivers (i.e. let the test system spin-up different versions of 
Cassandra prior to each test run).

TL;DR
Unless you have alternatives to the above, please make sure to support a simple 
test mode that connects to Cassandra on a configurable host and port.
                
> relocate Java (JDBC) CQL driver
> -------------------------------
>
>                 Key: CASSANDRA-3300
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3300
>             Project: Cassandra
>          Issue Type: Task
>          Components: Drivers
>            Reporter: Eric Evans
>            Priority: Minor
>              Labels: cql
>         Attachments: v1-0001-CASSANDRA-3300-remove-driver-build-test.txt
>
>
> A new project as been created at 
> http://code.google.com/a/apache-extras.org/p/cassandra-jdbc, a current 
> snapshot of the code from trunk has been imported, and the tests updated.
> I've configured commit notifications to be sent to 
> commits@cassandra.apache.org, though this can be changed if people object.
> To the best of my knowledge, the only thing remaining is to configure the 
> initial set of committers and admins.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to