cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From horschi <hors...@gmail.com>
Subject Re: How do you run integration tests for your cassandra code?
Date Mon, 13 Oct 2014 20:17:01 GMT
Hi Kevin,

I run my tests against my locally running Cassandra instance. I am not
using any framework, but simply truncate all my tables after/before each
test. With which I am quite happy.

You have to enable the unsafeSystem property, disable durable writes on the
CFs and disable auto-snapshot in the yaml for it to be fast.

kind regards,
Christian


On Mon, Oct 13, 2014 at 9:50 PM, Kevin Burton <burton@spinn3r.com> wrote:

> Curious to see if any of you have an elegant solution here.
>
> Right now I”m using cassandra unit;
>
> https://github.com/jsevellec/cassandra-unit
>
> for my integration tests.
>
> The biggest problem is that it doesn’t support shutdown.  so I can’t stop
> or cleanup after cassandra between tests.
>
> I have other Java daemons that have the same problem.  For example,
> ActiveMQ doesn’t clean up after itself.
>
> I was *thinking* of using docker or vagrant to startup a daemon in a
> container, then shut it down between tests.
>
> But this seems difficult to setup and configure … as well as being not
> amazingly portable.
>
> Another solution is to use a test suite, and a setUp/tearDown that drops
> all tables created by a test.   This way you’re still on the same cassandra
> instance, but the tables are removed for each pass.
>
> Anyone have an elegant solution to this?
>
> --
>
> Founder/CEO Spinn3r.com
> Location: *San Francisco, CA*
> blog: http://burtonator.wordpress.com
> … or check out my Google+ profile
> <https://plus.google.com/102718274791889610666/posts>
> <http://spinn3r.com>
>
>

Mime
View raw message