Re: Unit testing, Riak buckets

2013-10-14 Thread Daniil Churikov
misconfiguration of this environment or if the node crashes b/c of disk fullness how well your cluster tolerate this fault. -- View this message in context: http://riak-users.197444.n3.nabble.com/Unit-testing-Riak-buckets-tp4029451p4029464.html Sent from the Riak Users mailing list archive at Nabble.com

Re: Unit testing, Riak buckets

2013-10-13 Thread Sean Cribbs
https://github.com/basho/riak_test/blob/master/src/rtdev.erl#L76 is the main function that does the resetting of the git repository (and stops nodes, etc). https://github.com/basho/riak_test/blob/master/bin/rtdev-setup-releases.shcreates the necessary directory structure and git repo for rtdev.erl

Re: Unit testing, Riak buckets

2013-10-13 Thread Jeremiah Peschka
Go on. --- sent from a tiny portion of the hive mind... in this case, a phone On Oct 13, 2013 9:19 PM, "Sean Cribbs" wrote: > Not sure it's the greatest way (sometimes slow), but our integration > testing tool riak_test uses git to store a clean "devrel" and resets/cleans > the git repository at

Re: Unit testing, Riak buckets

2013-10-13 Thread Sean Cribbs
Not sure it's the greatest way (sometimes slow), but our integration testing tool riak_test uses git to store a clean "devrel" and resets/cleans the git repository at the beginning of each test. If you're curious, I can point you to the relevant sections of code that do this. On Sun, Oct 13, 2013

Re: Unit testing, Riak buckets

2013-10-13 Thread Jeremiah Peschka
For CorrugatedIron's integration tests, we frequently use a GUID as part of the bucket name and then destroy the bucket after tests finish. Since I'm frequently moving between different Riak builds, I destroy my data directories at the filesystem level on a regular basis. Your idea of using cron j

Unit testing, Riak buckets

2013-10-13 Thread Toby Corkindale
Hi, I'd like to hear how other people are approaching the problem of cleaning Riak buckets up at the end of unit tests for their apps. The problem I have is that multiple tests may be run at once (by different developers or different Jenkins' jobs or even just a parallelised test suite) so I