[
https://issues.apache.org/jira/browse/CASSANDRA-19978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17886994#comment-17886994
]
Stefan Miklosovic commented on CASSANDRA-19978:
-----------------------------------------------
I dont think sharing cluster across tests is a good idea. cassandra dtests
repository is spinning cluster every single test method if it is necessary. In
majority of cases, we will be starting 1 node cluster anyway. Benefit of not
being on CCM is that a developer does not need to mess up with Python + CCM.
Believe or not, somebody finds it dredful to deal with that when they do not
need to do that at all. gocql driver is Go-first project so I do not know why
we should rely on CCM.
> Rewrite integration test setup in Go
> ------------------------------------
>
> Key: CASSANDRA-19978
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19978
> Project: Cassandra
> Issue Type: Task
> Components: Client/gocql-driver
> Reporter: João Reis
> Priority: Normal
>
> {quote}Currently integration tests use ccm to setup a Cassandra cluster for
> testing.
> It is not easy to simulate things like topology changes, nodes joining,
> leaving, re-joining with a different IP address, etc.
> We could rewrite integration test runner using Docker API directly or using a
> library like testcontainers-go.
> {quote}
>
> https://github.com/apache/cassandra-gocql-driver/issues/1686
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
